What can you do with this server?

GitHub Repo MCP allows AI assistants to browse and explore GitHub repositories. With this server, you can: * Browse any public GitHub repository's contents, including root directories, subdirectories, and files * List all entries at any directory level within repositories * Retrieve and display the content of code and text files The server is compatible with MCP clients such as Cursor, Windsurf, and Claude Desktop (supporting the stdio protocol), offers easy installation via npm, yarn, or Smithery, and includes optional GitHub token authentication for higher API rate limits. Key tools provided include getRepoAllDirectories, getRepoDirectories, and getRepoFile for specific repository interactions.

Which integrations are available for this server?

Enables browsing public GitHub repositories, navigating through directories, and viewing file contents with tools for listing repository files and fetching specific file data.

How do I use github-repo-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@github-repo-mcp show me the README.md file from https://github.com/Ryan0204/github-repo-mcp" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

en es ja ko zh

github-repo-mcp

by Ryan0204

Overview Schema Related Servers Score Discussions

JavaScript

Remote

GitHub Repo MCP

Related MCP server: UIThub MCP Server

✨ Key features

💻 Compatible with Cursor, Windsurf, Claude Desktop, and other MCP clients supporting stdio protocol
🔎 Browse the contents of any public GitHub repository
📂 Navigate through repository directories and subdirectories
📝 View the content of code and text files
📦 Easy installation via package manager

Getting Started

Prerequisites

Installing the server requires the following on your system:

Node.js 18+
npm or yarn

Step 1. Installation

You can install and run GitHub Repo MCP using Smithery, NPX, or setting in mcp.json of your IDE:

MacOS

npx github-repo-mcp

Windows NPX

cmd /c npx -y github-repo-mcp

Windows NPX via .cursor/mcp.json

{
  "mcpServers": {
    "github-repo-mcp": {
      "command": "wsl",
      "args": [
        "bash",
        "-c",
        "cmd /c npx -y github-repo-mcp"
      ],
      "enabled": true
    }
  }
}

Windows NPX via .cursor/mcp.json (if path not set)

# Find the full path to npx first
which npx

{
  "mcpServers": {
    "github-repo-mcp": {
      "command": "wsl",
      "args": [
        "bash",
        "-c",
        "'/home/[username]/.nvm/versions/node/v20.18.0/bin/npx github-repo-mcp'"
      ],
      "enabled": true
    }
  }
}

Installing via Smithery

To install GitHub Repo MCP for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @Ryan0204/github-repo-mcp --client claude

Wait a few seconds or click on the refresh button a few times if it does not register. If it still won't register, make sure you entered the right command.

Step 2. Configuration

The GitHub Repo MCP server can use a GitHub token for higher rate limits when accessing the GitHub API.

Environment Variables

Variable	Required	Default	Description
`GITHUB_TOKEN`	No	None	Your GitHub personal access token for higher rate limits

Setting Up a GitHub Token (Optional)

While the server works without authentication, GitHub API has rate limits that are much lower for unauthenticated requests. To increase your rate limit:

Create a personal access token at https://github.com/settings/tokens
Set the token as an environment variable in mcp.json:

{
  "mcpServers": {
    "github-repo-mcp": {
      "command": "...",
      "args": [
        ...
      ],
      "env": {
        "GITHUB_TOKEN": "Your_Github_Token"
      }
      "enabled": true,
    }
  }
}

Feature Overview

Repository Browsing Tools

The server provides three main tools for interacting with GitHub repositories:

1. `getRepoAllDirectories`

Lists all files and directories at the root of a GitHub repository.

Parameters:
- repoUrl: The URL of the GitHub repository (e.g., "https://github.com/owner/repo")

2. `getRepoDirectories`

Lists contents of a specific directory in a GitHub repository.

Parameters:
- repoUrl: The URL of the GitHub repository
- path: The directory path to fetch (e.g., "src")

3. `getRepoFile`

Retrieves and displays the content of a specific file from a GitHub repository.

Parameters:
- repoUrl: The URL of the GitHub repository
- path: The file path to fetch (e.g., "src/index.js")

Usage Examples

Here are some examples of how to use these tools with an AI assistant:

Browsing a repository root: Ask your AI assistant to "Show me the contents of the repository at https://github.com/Ryan0204/github-repo-mcp"
Exploring a specific directory: Ask "What files are in the src directory of https://github.com/Ryan0204/github-repo-mcp?"
Viewing a file: Ask "Show me the README.md file from https://github.com/Ryan0204/github-repo-mcp"

Limitations

Rate Limiting: Without authentication, GitHub API has strict rate limits (60 requests per hour)
Private Repositories: Can only access public repositories unless a token with appropriate permissions is provided
Binary Files: The server detects common binary file extensions and won't display their contents
Large Files: GitHub API has limitations on the size of files that can be retrieved

Troubleshooting

Here are some common issues and their solutions:

Rate limit exceeded: Set up a GitHub token as described in the Configuration section
Command not found: Ensure the package is installed globally
Connection errors: Check your internet connection and GitHub API status

If you encounter any issues, please check the output for error messages or create an issue in the GitHub repository.

Enjoy! ☺️

Available Tools

3 tools

getRepoAllDirectoriesD

ParametersJSON Schema

Name	Required	Description	Default
`repoUrl`	Yes	The URL of the Github repo

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

getRepoDirectoriesD

ParametersJSON Schema

Name	Required	Description	Default
`path`	Yes	The directory path to fetch
`repoUrl`	Yes	The URL of the Github repo

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

getRepoFileD

ParametersJSON Schema

Name	Required	Description	Default
`path`	Yes	The file path to fetch
`repoUrl`	Yes	The URL of the Github repo

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.0.0Aug 14, 2025
- First observedgetRepoAllDirectories
- First observedgetRepoDirectories
- First observedgetRepoFile

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.4/5.0

Disambiguation2/5

The tools have overlapping purposes with unclear boundaries: getRepoAllDirectories and getRepoDirectories appear to serve similar directory-related functions without descriptions to clarify their differences, while getRepoFile is distinct but the directory tools are ambiguous. This overlap will likely cause misselection between the two directory tools.

Naming Consistency4/5

The naming follows a consistent camelCase pattern (getRepoAllDirectories, getRepoDirectories, getRepoFile) with a clear verb_noun structure, though the lack of descriptions makes it harder to assess intent. There are no deviations in style, but the similarity in names for the directory tools slightly reduces clarity.

Tool Count2/5

With only 3 tools, this server feels thin for a GitHub repository domain, as it lacks essential operations like create, update, delete, or search. The limited scope suggests incomplete coverage, making it difficult for agents to perform comprehensive repository management tasks.

Completeness1/5

The tool surface is severely incomplete for a GitHub repository server: it only includes retrieval tools for directories and files, missing core CRUD operations (e.g., create repo, update files, delete items), search functionality, and lifecycle management. This will cause significant agent failures in handling typical repository workflows.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Studex MCP ServerOAuth
io.github.itshivams
Model Context Protocol server for Studex tools, notifications, and profile integrations
Developer Tools
1
hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
237
saidsef-mcp-github-pr-issue-analyser
ai.smithery
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
Version Control Developer Tools Project Management
26
mcp COAuth
com.wix
A Model Context Protocol server for Wix AI tools
Developer Tools Content Management Systems App Automation
216

Related MCP Servers

MCP GitHub Repository Server
Version Control Developer Tools File Systems
loglmhq
A
license
Not graded
quality
D
maintenance
A server that allows AI assistants to browse and read files from specified GitHub repositories, providing access to repository contents via the Model Context Protocol.
Updated 2 years ago (2024-12-06 05:51 UTC)
6
MIT
UIThub MCP Server
Version Control Code Analysis
janwilmake
A
license
Not graded
quality
D
maintenance
Model Context Protocol server that enables Claude to retrieve and analyze code from GitHub repositories through the uithub API.
Updated 10 months ago (2025-11-05 03:58 UTC)
14
21
MIT
GitHub See MCP Server
Code Analysis Developer Tools Version Control
JesusMaster
F
license
Not graded
quality
D
maintenance
A server-side implementation that handles context processing between GitHub repositories and AI models, enabling seamless integration of AI capabilities with codebases through the Model Context Protocol.
Updated 9 months ago (2025-12-02 01:01 UTC)
1
-
GitHub Tools MCP Server
Version Control Developer Tools Search
arjunkmrm
F
license
Not graded
quality
Not graded
maintenance
Model Context Protocol server that enables interaction with GitHub repositories, issues, pull requests, and search functionality through natural language.
Updated a year ago (2025-05-15 07:29 UTC)
1
-

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Ryan0204/github-repo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

GitHub Repo MCP

Table of contents

✨ Key features

Getting Started

Prerequisites

Step 1. Installation

MacOS

Windows NPX

Windows NPX via .cursor/mcp.json

Windows NPX via .cursor/mcp.json (if path not set)

Installing via Smithery

Step 2. Configuration

Environment Variables

Setting Up a GitHub Token (Optional)

Feature Overview

Repository Browsing Tools

1. getRepoAllDirectories

2. getRepoDirectories

3. getRepoFile

Usage Examples

Limitations

Troubleshooting

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

1. `getRepoAllDirectories`

2. `getRepoDirectories`

3. `getRepoFile`