Docdex MCP Server

Fast per-repo documentation indexer and full-text search MCP server for codebases.

Remote serverstreamable-httpPython

What is the Docdex MCP server?

Fast per-repo documentation indexer and full-text search MCP server for codebases. Exposed over MCP by the docdex mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Docdex is a local-first indexer and search daemon for documentation and source code. It sits between your raw files and your AI assistant, providing deterministic search, code intelligence, and persistent memory without ever uploading your code to a cloud vector store.

Its toolset

Everything the assistant can do here goes through one of these:

  • Architecture — Use the daemon HTTP/SSE endpoint. For sandboxed clients, Docdex can also serve MCP over local IPC (Unix socket or Windows named pipe), while HTTP/SSE
  • Security — The Security tool exposed by this server

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need one environment variable: DOCDEX_OLLAMA_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Docdex's toolset — Architecture, Security — is a fair guide to whether it matches your workflow. It is maintained by bekirdag; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Docdex's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the docdex mcp server does with a few real requests.

Available tools

ToolWhat it does
ArchitectureUse the daemon HTTP/SSE endpoint. For sandboxed clients, Docdex can also serve MCP over local IPC (Unix socket or Windows named pipe), while HTTP/SSE remains the default for most MCP clients.
SecurityThe Security tool exposed by this server.

How to install the Docdex MCP server

{
  "mcpServers": {
    "docdex": {
      "command": "npx",
      "args": ["-y", "docdex"],
      "env": {
        "DOCDEX_OLLAMA_BASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
DOCDEX_OLLAMA_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Docdex to Architecture.
  • Use Docdex to Security.

Frequently asked questions

It connects Docdex to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Architecture, Security) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Docdex directly.