Difficulty / est. effort: ~1-2h, small-medium (docs + config)
Context: JetBrains Rider is the JetBrains .NET IDE (and IntelliJ the JVM flagship); the AI Assistant supports MCP. A recipe lets Rider/IntelliJ users consult an OKF bundle via okf-mcp (a standard stdio MCP server; src/OKF4net.Mcp/README.md documents only Claude today).
Files to touch: src/OKF4net.Mcp/README.md (add a ### Use with JetBrains Rider (and IntelliJ) section).
What to do:
- Add the section covering Rider and, where identical, IntelliJ IDEA.
- Document how to register the server via the AI Assistant MCP settings (Settings → Tools → AI Assistant → Model Context Protocol) and/or an
mcp.json, with command: "okf-mcp" + bundle-path args. Verify the exact path/schema and minimum IDE version against current JetBrains docs and link them.
- Mention
OKF_MCP_READONLY=1.
How to verify:
dotnet tool install -g OKF4net.Mcp (installs okf-mcp).
- Point the config at a small test bundle (e.g.
tests/fixtures/ has example bundles, or make a throwaway one with a single type:-tagged concept).
- Restart the editor, open its MCP/agent panel, and confirm the
okf server 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=1 note 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.
Difficulty / est. effort: ~1-2h, small-medium (docs + config)
Context: JetBrains Rider is the JetBrains .NET IDE (and IntelliJ the JVM flagship); the AI Assistant supports MCP. A recipe lets Rider/IntelliJ users consult an OKF bundle via
okf-mcp(a standard stdio MCP server;src/OKF4net.Mcp/README.mddocuments only Claude today).Files to touch:
src/OKF4net.Mcp/README.md(add a### Use with JetBrains Rider (and IntelliJ)section).What to do:
mcp.json, withcommand: "okf-mcp"+ bundle-pathargs. Verify the exact path/schema and minimum IDE version against current JetBrains docs and link them.OKF_MCP_READONLY=1.How to verify:
dotnet tool install -g OKF4net.Mcp(installsokf-mcp).tests/fixtures/has example bundles, or make a throwaway one with a singletype:-tagged concept).okfserver connects and the OKF tools appear (okf_read_concept,okf_browse,okf_graph,okf_search,okf_validate_bundle,okf_changes_since).OKF_MCP_READONLY=1note for read-only use.Docs-only change — no build impact — but run
dotnet build OKF4net.slnto be safe.Good to know: Model the new section on the existing "Use with Claude Desktop" block in
src/OKF4net.Mcp/README.md(samecommand: "okf-mcp"+ bundle-pathargs, orOKF_BUNDLE_ROOTenv). 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.