GitHub

Converts GitHub repositories into runnable MCP servers that expose tools to read, search, and interact with codebases.
  • typescript

9

GitHub Stars

typescript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "nirholas-github-to-mcp": {
      "command": "node",
      "args": [
        "server.mjs"
      ],
      "env": {
        "GITHUB_TOKEN": "ghp_xxxxx"
      }
    }
  }
}

You transform a GitHub repository into a fully functional MCP server that AI assistants can query and interact with. This enables code-aware agents to read files, search code, list directories, and invoke repository-defined tools without manual context setup, turning any codebase into a structured, explorable API for automation and analysis.

How to use

You run the generated MCP server and connect it to your preferred MCP client. The server exposes tools derived from the repository contents, such as reading files, listing files, searching code, and calling API-like tools discovered within the codebase. Use an MCP client to list available tools, call a tool with its required inputs, and receive structured responses that you can feed back into your prompt or automation workflow.

How to install

Prerequisites: Node.js 22+ and a JavaScript/TypeScript development environment. You will typically build the generated MCP server package from the repository you analyzed and then run the server.

# Basic local setup (example flow)
# 1) Clone the source that generates the MCP server

git clone https://github.com/nirholas/github-to-mcp.git
cd github-to-mcp

# 2) Install dependencies (uses pnpm in this project by default)
pnpm install

# 3) Build the packages
pnpm build

# 4) Run the generated MCP server manually (stdio transport)
node server.mjs
```} ,{

Configuration

The MCP server can be run with stdio (local process) or HTTP (remote server). The following setup demonstrates a local server using Node and the generated server file. Ensure you have any required environment variables in place, such as a GitHub token if private repositories are used.

{
  "mcpServers": {
    "github_to_mcp": {
      "type": "stdio",
      "name": "github_to_mcp",
      "command": "node",
      "args": ["server.mjs"]
    }
  },
  "env": {
    "GITHUB_TOKEN": "YOUR_GITHUB_TOKEN"
  }
}

Examples and tips

After starting the server, you can connect from Claude Desktop, Cursor, Continue, or any MCP-compatible client. Use the client’s configuration to point to the local stdio server or to the provided HTTP URL if you deploy the server behind an HTTP gateway.

Troubleshooting

If you encounter rate limits when accessing GitHub data, supply a GitHub token with appropriate scopes. If the server cannot start, verify you are using Node.js 22+ and that the generated server file path shown in startup commands exists.

Available tools

get_readme

Retrieve the repository's README content.

list_files

List files and directories at a given path.

read_file

Read the contents of a specific file.

search_code

Search patterns across the repository.

readme_examples_tool

Tools inferred from README examples to demonstrate command usage.

analyze_sentiment

Analyze sentiment of input text, as shown in sample code tools.

get_user

Fetch user data from API specifications or docs.

list_users

List user-like resources from API or documentation sources.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational