Use Repokit through the hosted MCP interface.

What this page is for

Repokit MCP exposes repository-aware retrieval as a hosted MCP product for clients that already understand tool-based workflows.

The engine boundary still lives at the Repokit API. This page is the human-facing setup path; the raw hostnames below are technical transport targets, not alternate landing pages.

How MCP relates to the API

• The Repokit API is the direct engine contract.
• Repokit MCP is the first-party MCP interface powered by that API.
• Use the API when you want direct HTTP control.
• Use MCP when your client already supports remote MCP servers.

Important endpoint distinction

• repokit.co/mcp is the page readers should start with.
• mcp.repokit.live is the hosted MCP service root.
• /mcp is the JSON-RPC protocol endpoint.
• Initialize can be unauthenticated, but tool calls require bearer auth.

Initialize example

curl -sS -X POST \
  -H "Content-Type: application/json" \
  https://mcp.repokit.live/mcp \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-03-26",
      "capabilities": {},
      "clientInfo": {
        "name": "example-client",
        "version": "0.1"
      }
    }
  }'

Authenticated tool call

curl -sS -X POST \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <your_token>" \
  https://mcp.repokit.live/mcp \
  -d '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": {
      "name": "find_relevant_files",
      "arguments": {
        "repository_id": "<repository_id>",
        "query": "fix request validation error in routing",
        "top_k": 3
      }
    }
  }'

What a successful flow looks like

• Activate a supported repository.
• Wait until it reaches ready.
• Issue a verification token.
• Initialize the hosted MCP endpoint.
• Call find_relevant_files.

When to use MCP

• Your client already supports MCP.
• You want tool-style access instead of wiring raw API requests yourself.
• You want the same retrieval layer through a first-party MCP transport.