Repo-to-RAG MCP Server

by evozim Your server? Claim it

answering

Repo-to-RAG is answering right now. Last checked 1 min ago.

GitHub repository vectorizer and context synthesizer for RAG pipelines.

Uptime history 47 days of history · worst day 99%

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

91 ms

Response time

average over 24h

authentication required

Access

sse

Nothing serious here today

Today is the operative word: we check Repo-to-RAG every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add repo-to-rag --transport http https://repo-to-rag-mcp.vercel.app/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "repo-to-rag": {
      "url": "https://repo-to-rag-mcp.vercel.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.repo-to-rag]
url = "https://repo-to-rag-mcp.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "repo-to-rag": {
      "url": "https://repo-to-rag-mcp.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "repo-to-rag": {
      "url": "https://repo-to-rag-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://repo-to-rag-mcp.vercel.app/api/mcp	sse	needs auth	79 ms	1 min ago

Alternatives to Repo-to-RAG

same job, measured the same way

Project Context

by sandovalrr

Safely manage repository-scoped issues across Linear, GitHub Issues, and Jira Cloud.

51 installs/wk local only

Octocode MCP - AI Context Platform

by bgauryy

AI code research platform. Search, analyze, and extract insights from any GitHub repository.

1 867 installs/wk local only

Bitbucket MCP Server

by lawp09

MCP server for Bitbucket API - manage repositories, pull requests, comments, pipelines and more

447 installs/wk local only

RepoContext

by shmindmaster

Read-only, commit-pinned repository context for coding agents.

local only

Github Repo MCP

by thedhruv-07

MCP server for GitHub repo health, commit summaries, issue triage, and RAG Q&A.

143 installs/wk local only

LeanToken

by morluto

Token-bounded repository context for coding agents over MCP.

local only

Github Analytics MCP Server

by thenextgennexus

Get GitHub repository stats, search repos, analyze languages, and compare projects

20 installs/wk local only

Moxie Docs

by jackalope-dev

Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.

12 tools answering

Repo-to-RAG — questions

Answers built from our own checks of this server.

Why is there no tool list for Repo-to-RAG?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Repo-to-RAG working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 91 ms. The bar chart above shows every period we have measured.

How do I connect Repo-to-RAG?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Repo-to-RAG need an API key?

Yes. Every time we knock, Repo-to-RAG answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Repo-to-RAG?

It answers our handshake in 91 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.