Repo-to-RAG MCP Server

by evozim Your server? Claim it

answering

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

GitHub repository vectorizer and context synthesizer for RAG pipelines.

Uptime history 91 days of history · worst day 0%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

104 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 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "repo-to-rag": {
      "type": "sse",
      "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	97 ms	14 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.

67 installs/wk local only

Appveyor MCP

by mrfentmen

CI pipeline monitoring for GitLab and GitHub - no API key.

299 installs/wk local only

Octocode MCP - AI Context Platform

by bgauryy

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

3 681 installs/wk local only

Mikie

by getmikie

Focused repository context for Claude Code and Codex, with per-session token usage receipts.

2 506 installs/wk local only

GitHubCard

by githubcard

Create GitHub profile and repository cards for READMEs, link previews and social posts.

answering

Bitbucket MCP Server

by lawp09

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

1 079 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.

32 installs/wk local only

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 91 of 91 checks got a reply (100.0%), average response time 104 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 in the form 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 104 ms on average, which is faster than 92% 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.