Developer · Remote MCP server

RepoFuse

Discover and scaffold new apps by reusing code from your GitHub repositories.

Visit RepoFuse's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
com.repofuse/repofuse
Version
0.3.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-09-27
Updated
2026-09-27
Publisher
com.repofuse
Namespace
Namespace verified by the MCP Registry via the domain repofuse.com · how
Listed under
GitHub MCP servers
Website
repofuse.com/mcp
Repository
github.com/DealPatrol/RepoFuse
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://repofuse.com/api/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

How to connect RepoFuse

RepoFuse is a remote MCP server: there is nothing to install. Its endpoint is https://repofuse.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
repo-memory-mcpPersistent local memory for MCP-compatible AI coding agents, stored per repository in SQLite.Local · stdioPyPI: repo-memory-mcp-ai
repo2graphAsk a codebase a question, get back the source that answers it - every block cited to file:line.Local · stdioPyPI: repo2graph
RepoContextRead-only, commit-pinned repository context for coding agents.Local · stdionpm: @shmindmaster/repocontext
repoctxLocal-first code context, impact analysis, and merge-readiness verdicts for AI agents.Local · stdionpm: @nugehs/repoctx
RepoGatesTrust verdicts on repos, models, VS Code and Docker Desktop extensions and agent skills.Remote · HTTPLive check: sign-in requiredmcp.repogates.com
Repology MCPRepology: package versions across many software repositories.Local · stdionpm: repology-mcp
repomapA map of your codebase for AI agents: code graph, search, call paths and change impact. No API key.Local · stdionpm: @sylphx/repomap
RepomemoryPersistent memory for AI coding agents. Hybrid search, auto-session capture, context routing.Local · stdionpm: repomemory