Repo-to-RAG

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

GitHub repository vectorizer and context synthesizer for RAG pipelines.

VerifiedSSEWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

A remote MCP server that vectorizes GitHub repositories and synthesizes context for RAG pipelines.

What you can do
Turns a GitHub repository into vectorized content for retrieval-augmented generation workflows, based on the registry description. Synthesizes context from repository content so an assistant can work with codebase material in RAG pipelines. No tool list is published, so the exact operations available are not documented.
When to use it
Worth considering when you want an assistant to build or feed a RAG pipeline from GitHub repository content without running local tooling.
Requirements
Connect to the remote SSE endpoint at repo-to-rag-mcp.vercel.app; no local package or runtime is declared. No authentication is declared, but a payment-signature header is listed as a secret, described as required for premium settlement.
Before you install
The server asks for a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature, which authorizes a payment; treat it as a spending credential and only supply it if you accept the charge. Repository content is sent to a third-party hosted endpoint. No tool list or README is provided, so behavior is unverified.

Installation

In SourceWeft

  1. Open Repo-to-RAG in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Frepo-to-rag/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.