src-to-kb

This MCP server enables integration with Claude Code and Cursor for the Source Code to Knowledge Base (src-to-kb) workflow. Once running, IDEs and tooling can query the MCP service to fetch context-aware information, losslessly connect code chunks to their semantic knowledge, and help users navigate large codebases through the integrated assistant. The server leverages the same Sapience-aware capabilities exposed by the src-to-kb suite (chunking, embeddings, and API access) and exposes an MCP-compatible interface so external tools can request code-contextual responses, embeddings, and search results efficiently. Typical usage involves starting the MCP server, configuring your Claude/Cursor integration to point at the MCP endpoint, and using the src-to-kb-mcp-enabled features from your IDE to request contextual insights during coding sessions.

With this MCP server enabled, you can expect to work with capabilities such as: querying code context for a given function or snippet, retrieving relevant knowledge-base chunks to inform coding decisions, and performing code-aware searches that leverage the knowledge base and embeddings generated by the src-to-kb toolchain. It complements the existing CLI commands (src-to-kb, src-to-kb-search, src-to-kb-upload, src-to-kb-api) by offering a persistent, IDE-friendly interface for real-time assistance during development.

Prerequisites:

• Node.js and npm installed on the system
• Access to the internet to install dependencies

1. Install the src-to-kb MCP server globally (recommended):

   npm install -g @vezlo/src-to-kb

2. Verify installation

   src-to-kb-mcp --version

3. Configure environment (optional but recommended):

   • If you plan to use external servers or authenticated services, set:
     • EXTERNAL_KB_URL (URL of the external knowledge base server)
     • EXTERNAL_KB_API_KEY (API key for the external server, if required)
   • If using Claude Code/Cursor integrations, provide your API keys as needed by your tooling (e.g., CLAUDE_API_KEY).

4. Start the MCP server:

   src-to-kb-mcp

5. (Optional) Integrate with your IDE or Claude/Cursor by pointing them to the MCP endpoint provided by the server. Follow the specific IDE plugin or tooling docs to configure MCP endpoint URLs and authentication if applicable.

Tips and common considerations:

• The MCP server is designed to work alongside the main src-to-kb tooling. Ensure your environment variables for external server integration are set when you intend to route processing through an external knowledge base server.
• If you enable embeddings and external search, ensure you have OPENAI_API_KEY or equivalent credentials configured for embedding generation.
• For Notion and external data sources, the same processing modes apply; the MCP server will relay contextual information to Claude/Cursor as applicable.
• When using external servers, remember to set EXTERNAL_KB_URL and EXTERNAL_KB_SEARCH_URL as needed to route knowledge items and search queries.
• If you encounter connectivity issues, verify network access to the external server and ensure the MCP endpoint port is reachable from your IDE or client tooling.