Endpoints
- Host root: https://mcp.repokit.live
- HTTP MCP endpoint: https://mcp.repokit.live/mcp
Authentication
Initialize can be unauthenticated, but authenticated tool calls should use the verification token issued for your ready repository.
Initialize example
initializebash
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": "repo-intelligence-docs-example",
"version": "1.0.0"
}
}
}'Tools list example
tools/listbash
curl -sS -X POST \
-H "Content-Type: application/json" \
https://mcp.repokit.live/mcp \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/list",
"params": {}
}'Tool call example
tools/callbash
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
}
}
}'When to use MCP instead of the API
- Your client already supports MCP.
- You want tool-style access rather than direct endpoint wiring.
- You want a simpler agent integration path for repository-aware retrieval.
Related docs