Kindex MCP Server

Persistent knowledge graph and MCP server for AI workflows with git-tracked project context. Exposed over MCP by the kindex mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

It's a persistent knowledge graph for AI-assisted workflows. It indexes your conversations, projects, and intellectual work so that Claude Code, Codex, Gemini CLI, Google Antigravity, OpenCode, Cursor, and other MCP-capable agents never start a session blind. Available as a free MCP plugin or standalone CLI.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Its toolset

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

• payments-refactor — 2 unread (focus: Extract billing service)
• Extra — Adds
• mcp — kin-mcp MCP server (for Claude Code, Codex, Gemini, Antigravity, OpenCode, Cursor, etc.)
• llm — Anthropic-powered extraction (kin learn, kin ask)
• vectors — sqlite-vec for semantic similarity search
• reminders — Natural-language time parsing for kin remind
• all — Everything above
• Tier — Budget
• full — ~4000 tokens
• abridged — ~1500 tokens
• summarized — ~750 tokens
• executive — ~200 tokens

Configuration

You will need 5 environment variables: CLAUDE_SESSION_ID, CODEX_SESSION_ID, OPENCODE_SESSION_ID, CURSOR_SESSION_ID, KIN_AGENT_ID. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Kindex.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the kindex mcp server does with a few real requests.

When to reach for it

Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Kindex's toolset — payments-refactor, Extra, mcp and 11 more — is a fair guide to whether it matches your workflow. It is maintained by jmcentire; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.