Claude MCP Server

Search Claude Code conversation history with natural language queries across all projects

Local serverstdioTypeScript

What is the Claude MCP server?

Claude MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Search Claude Code conversation history with natural language queries across all projects.

What you get

Find any conversation across all projects: bash "where did we discuss the database issue?" "find that authentication conversation" "docker configuration we talked about yesterday"

Setting it up

The server ships on npm as claude-code-conversation-search-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Claude is connected, these are the calls the assistant has available:

  • Contributing — 1. Fork the repository 2. Create a feature branch (git checkout -b feature/amazing-feature) 3. Commit your changes (git commit -m 'Add amazing

Configuration and credentials

You will need 2 environment variables: DEBUG, CONVERSATION_DB_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • 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.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the claude mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling 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. Claude's toolset — Contributing — is a fair guide to whether it matches your workflow. It is maintained by TonySimonovsky; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
Contributing1. Fork the repository 2. Create a feature branch (git checkout -b feature/amazing-feature) 3. Commit your changes (git commit -m 'Add amazing feature') 4. Push to the branch (git push origin feature/amazing-feature) 5.

How to install the Claude MCP server

```json
{
  "mcpServers": {
    "conversation-search": {
      "command": "claude-code-conversation-search-mcp",
      "args": []
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
DEBUGConfiguration value read at startup.Optional
CONVERSATION_DB_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Claude to Contributing.

Frequently asked questions

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