en es ja ko zh

github-repo-mcp

Name: github-repo-mcp
Author: Ryan0204

by Ryan0204

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

GitHub 仓库 MCP

铁匠徽章

✨ 主要特点

💻 兼容 Cursor、Windsurf、Claude Desktop 和其他支持stdio协议的 MCP 客户端
🔎 浏览任何公共 GitHub 存储库的内容
📂 浏览存储库目录和子目录
📝 查看代码和文本文件的内容
📦通过包管理器轻松安装

入门

先决条件

安装服务器需要您的系统具备以下条件：

Node.js 18+
npm 或 yarn

步骤1.安装

您可以使用 Smithery、NPX 或 IDE 的 mcp.json 中的设置来安装和运行 GitHub Repo MCP：

MacOS

npx github-repo-mcp

Windows NPX

cmd /c npx -y github-repo-mcp

通过 .cursor/mcp.json 实现 Windows NPX

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

通过 .cursor/mcp.json 的 Windows NPX（如果未设置路径）

# 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
    }
  }
}

通过 Smithery 安装

要通过Smithery自动为 Claude Desktop 安装 GitHub Repo MCP：

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

如果未注册，请等待几秒钟或点击刷新按钮几次。如果仍然无法注册，请确保您输入了正确的命令。

步骤2.配置

GitHub Repo MCP 服务器在访问 GitHub API 时可以使用 GitHub 令牌来获得更高的速率限制。

环境变量

多变的	必需的	默认	描述
`GITHUB_TOKEN`	不	没有任何	您的 GitHub 个人访问令牌，用于更高的速率限制

设置 GitHub 令牌（可选）

虽然服务器无需身份验证即可运行，但 GitHub API 对未经身份验证的请求的速率限制要低得多。要提高速率限制：

在https://github.com/settings/tokens创建个人访问令牌
在 mcp.json 中将令牌设置为环境变量：

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

功能概述

存储库浏览工具

该服务器提供了三个与 GitHub 存储库交互的主要工具：

1. `getRepoAllDirectories`

列出 GitHub 存储库根目录下的所有文件和目录。

参数：
- repoUrl ：GitHub 存储库的 URL（例如“ https://github.com/owner/repo ”）

2. `getRepoDirectories`

列出 GitHub 存储库中特定目录的内容。

参数：
- repoUrl ：GitHub 存储库的 URL
- path ：要获取的目录路径（例如“src”）

3. `getRepoFile`

从 GitHub 存储库检索并显示特定文件的内容。

参数：
- repoUrl ：GitHub 存储库的 URL
- path ：要获取的文件路径（例如“src/index.js”）

使用示例

以下是如何将这些工具与 AI 助手一起使用的一些示例：

浏览存储库根目录：要求您的 AI 助手“向我显示https://github.com/Ryan0204/github-repo-mcp存储库的内容”
探索特定目录：询问“ https://github.com/Ryan0204/github-repo-mcp的 src 目录中有哪些文件？”
查看文件：询问“显示https://github.com/Ryan0204/github-repo-mcp中的 README.md 文件”

限制

速率限制：如果没有身份验证，GitHub API 有严格的速率限制（每小时 60 个请求）
私有存储库：除非提供具有适当权限的令牌，否则只能访问公共存储库
二进制文件：服务器检测常见的二进制文件扩展名，但不会显示其内容
大文件：GitHub API 对可检索文件的大小有限制

故障排除

以下是一些常见问题及其解决方案：

超出速率限制：按照配置部分中的说明设置 GitHub 令牌
未找到命令：确保包已全局安装
连接错误：检查您的互联网连接和 GitHub API 状态

如果您遇到任何问题，请检查输出中的错误消息或在 GitHub 存储库中创建问题。

尽情享受吧！☺️

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.

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

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.4/5.0

Scored 2026-04-18 10:20 across 3 tools

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

ActivityMaintained

ResponsivenessNo issues

Resources

Need Help?

Reddit Discussion

Related Servers

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
238
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 a year ago (2025-11-05 03:58 UTC)
4 npm
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 10 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
-

GitHub 仓库 MCP

目录

✨ 主要特点

入门

先决条件

步骤1.安装

MacOS

Windows NPX

通过 .cursor/mcp.json 实现 Windows NPX

通过 .cursor/mcp.json 的 Windows NPX（如果未设置路径）

通过 Smithery 安装

步骤2.配置

环境变量

设置 GitHub 令牌（可选）

功能概述

存储库浏览工具

1. getRepoAllDirectories

2. getRepoDirectories

3. getRepoFile

使用示例

限制

故障排除

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches

1. `getRepoAllDirectories`

2. `getRepoDirectories`

3. `getRepoFile`