Document how to use the OKF4net MCP server with VS Code
Maintainers usually reply within 1 day
@laurentkempe is already working on this.
Since Sep 8, 2026.
Assessment
This issue has not been assessed yet.
Description
Difficulty / est. effort: ~1h, small (docs + config)
Context: OKF4net.Mcp (okf-mcp) is a standard stdio MCP server, but src/OKF4net.Mcp/README.md only documents Claude Desktop/Code. VS Code has first-class MCP support (agent mode / GitHub Copilot), so a short recipe lets any VS Code user consult an OKF bundle from the editor.
Files to touch: src/OKF4net.Mcp/README.md (add a ### Use with VS Code section); optionally cross-link from the root README.md "Use OKF in Claude (MCP)" section.
What to do:
- Add a
### Use with VS Codesection tosrc/OKF4net.Mcp/README.md. - Show a workspace
.vscode/mcp.json(VS Code uses a"servers"object, each entry with"type": "stdio","command": "okf-mcp", and the bundle path in"args"), plus the user-levelmcp.jsonalternative. Reference the current VS Code MCP docs: https://code.visualstudio.com/docs/copilot/chat/mcp-servers - Mention enabling the server in agent mode and the
OKF_MCP_READONLY=1option.
How to verify:
dotnet tool install -g OKF4net.Mcp(installsokf-mcp).- Point the config at a small test bundle (e.g.
tests/fixtures/has example bundles, or make a throwaway one with a singletype:-tagged concept). - Restart the editor, open its MCP/agent panel, and confirm the
okfserver connects and the OKF tools appear (okf_read_concept,okf_browse,okf_graph,okf_search,okf_validate_bundle,okf_changes_since). - Ask the assistant to read or browse a concept from the bundle and confirm it works. Add a
OKF_MCP_READONLY=1note for read-only use.
Docs-only change — no build impact — but run dotnet build OKF4net.sln to be safe.
Good to know: Model the new section on the existing "Use with Claude Desktop" block in src/OKF4net.Mcp/README.md (same command: "okf-mcp" + bundle-path args, or OKF_BUNDLE_ROOT env). MCP is a standard stdio protocol, so the server itself needs no change — only the client-side config differs. See CONTRIBUTING.md. If you get stuck on a config format, open a Discussion.
- Dominant language
- C#
- Stars
- 4
- Forks
- 1
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 32
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jchable/okf4net
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
.NET bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
test
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area/backend type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
umbraco/Umbraco-CMS#24668 · 1 comment ·
Maintainers usually reply within 1 day
-
Pri3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MicrosoftDocs/windows-dev-docs#6205 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
area-ai untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/extensions#7956 ·
Maintainers usually reply within 1 day