Already connected to the Framework MCP server for
planning work? You likely don’t need this — its
knowledge_ask tool
already proxies into the Knowledge Base for you. Connect directly to the
Knowledge Base MCP server only if you want Knowledge Base search/retrieval
from a session or client that isn’t otherwise talking to the Framework MCP
server. See Knowledge Base MCP Server: Overview
for the full comparison.Step 1: Get your server URL
Unlike the Framework MCP server, there’s currently no organization settings page that generates a pre-filled connection command for the Knowledge Base MCP server — you’ll need the URL from your administrator or deployment:- Local development:
http://localhost:8082(the server’s default port). - Production:
https://kbmcp.engineeringframework.dev— the hosted Knowledge Base MCP server. If your organization runs its own deployment, ask your administrator for that URL instead.
Step 2: Add MCP Server to Claude Code
Run this command in your terminal:.claude/settings.json manually:
Step 3: Add to your CLAUDE.md (optional)
If you want standing context so Claude reaches for the Knowledge Base without being asked, add a section like this to your repository’sCLAUDE.md:
ask and get_by_id.
Step 4: Verify your setup
- In your terminal, navigate to your repository
- Ensure
.claude/settings.jsonhas been updated with the MCP server config - Run
claudeto start a session - Try: “Search the Knowledge Base for anything about <a topic you know is documented>”
/mcp path and that
your session has access to the same tenant the Knowledge Base MCP
server is configured against — it’s the same login you use for the
Engineering Framework dashboard.
Using a different AI coding tool instead of Claude Code? See
Connecting Other AI Tools for OpenAI Codex,
GitHub Copilot, and Gemini CLI configuration.