Inkeep MCP Server

If you want an AI assistant working directly with Inkeep, the inkeep mcp server is the bridge. RAG Search over your content powered by Inkeep.

What Inkeep does

Note the full path of the project, referred to as <YOUR_INKEEP_MCP_SERVER_ABSOLUTE_PATH> in a later step.

Tools it exposes

Once connected, the assistant can call this tool directly:

• Dependencies — The Dependencies tool exposed by this server

Installing the inkeep mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 7 environment variables: INKEEP_API_BASE_URL, INKEEP_API_KEY, INKEEP_API_MODEL, INKEEP_MCP_TOOL_NAME, INKEEP_MCP_TOOL_DESCRIPTION, YOUR_INKEEP_MCP_SERVER_ABSOLUTE_PATH, YOUR_INKEEP_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

AI-service servers chain other models into your assistant, turning a single chat into a small production pipeline. Inkeep sits in that group, and the shape of its toolset — Dependencies — tells you what it is really for. Worth comparing against the other ai services servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the inkeep mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.