commit-to-pr-mcp
An MCP server that enables AI agents to retrieve detailed GitHub Pull Request information using git commit hashes, branch names, or PR numbers. It automatically detects repositories and extracts comprehensive PR data including descriptions, labels, and reviews via the GitHub CLI.
README
commit-to-pr-mcp
An MCP (Model Context Protocol) server that enables AI agents to extract PR details from git commit hashes using the GitHub CLI.
Features
- Commit to PR Resolution: Automatically extracts PR numbers from commit hashes, merge commits, and squash commits
- Auto-Detection: Automatically detects GitHub repository from git working directory
- Comprehensive PR Data: Retrieves full PR details including title, description, author, status, labels, and reviews
- Flexible Input: Accepts commit hashes (full or short), branch names, or direct PR numbers
- Type-Safe: Built with TypeScript and Zod for runtime validation
Prerequisites
- Node.js >= 18.0.0
- GitHub CLI installed and authenticated (
gh auth login) - An MCP-compatible client (Cursor, Claude Desktop, VS Code, etc.)
Installation
Getting Started
First, install the commit-to-pr-mcp server with your client.
Standard config works in most tools:
{
"mcpServers": {
"commit-to-pr": {
"command": "npx",
"args": [
"commit-to-pr-mcp@latest"
]
}
}
}
<details> <summary>Claude Code</summary>
Use the Claude Code CLI to add the server:
claude mcp add commit-to-pr npx commit-to-pr-mcp@latest
</details>
<details> <summary>Claude Desktop</summary>
Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"commit-to-pr": {
"command": "npx",
"args": ["commit-to-pr-mcp@latest"]
}
}
}
</details>
<details> <summary>Cursor</summary>
Click the button to install:
Or install manually:
Go to Cursor Settings → MCP → Add new MCP Server. Name to your liking, use command type with the command npx commit-to-pr-mcp@latest. You can also verify config or add command arguments via clicking Edit.
Project-Specific Configuration
Create .cursor/mcp.json in your project root:
{
"mcpServers": {
"commit-to-pr": {
"command": "npx",
"args": ["commit-to-pr-mcp@latest"]
}
}
}
</details>
<details> <summary>VS Code</summary>
Follow the MCP install guide, use the standard config above.
Alternatively, install using the VS Code CLI:
code --add-mcp '{"name":"commit-to-pr","command":"npx","args":["commit-to-pr-mcp@latest"]}'
</details>
<details> <summary>Cline</summary>
Add via the Cline VS Code extension settings or by updating your cline_mcp_settings.json file:
{
"mcpServers": {
"commit-to-pr": {
"command": "npx",
"args": [
"commit-to-pr-mcp@latest"
]
}
}
}
</details>
<details> <summary>Zed</summary>
Follow the MCP Servers documentation. Use the standard config above.
</details>
Local Development
For local development and testing:
{
"mcpServers": {
"commit-to-pr": {
"command": "node",
"args": ["/absolute/path/to/commit-to-pr-mcp/dist/index.js"],
"env": {
"LOG_LEVEL": "debug"
}
}
}
}
Verify Installation
After installation, verify commit-to-pr-mcp is working:
- Restart your MCP client completely
- Check connection status:
- Cursor: Look for green dot in Settings → Tools & Integrations → MCP Tools
- Claude Desktop: Check for "commit_to_pr" in available tools
- VS Code: Verify in GitHub Copilot settings
- Test with a simple query:
Get PR details for commit abc123
If you see the AI agent use the get_pr tool and return PR information, you're all set! 🎉
Usage
The server provides a single tool: get_pr
Basic Example: Get PR from Commit Hash
{
"commit": "abc123def456",
"repo": "owner/repo" // Optional: auto-detected from git working directory
}
Example: Get PR from Branch Name
{
"commit": "feature/new-feature",
"cwd": "/path/to/repo" // Optional: specify working directory for auto-detection
}
Example: Get PR by Number Directly
{
"pr_number": 42,
"repo": "owner/repo" // Optional: auto-detected from git working directory
}
Example: Auto-Detect Repository
When working in a git repository, you can omit the repo parameter:
{
"commit": "abc123"
// Repository is automatically detected from git remote
}
Tool Parameters
get_pr
Get PR details by commit hash or PR number. Extracts PR number from git commits (merge commits, squash commits) and returns full PR details.
Parameters:
commit(optional): Git commit hash (full or short), branch name, or any git reference. Use this ORpr_number.pr_number(optional): PR number to look up directly. Use this ORcommit.repo(optional): GitHub repository inowner/repoformat. If not provided, auto-detects fromcwdor current working directory.cwd(optional): Working directory path to auto-detect the GitHub repository from git remote.
Note: Either commit or pr_number must be provided.
Response Format
The tool returns a structured response:
{
"number": 42,
"title": "Add new feature",
"body": "This PR adds a new feature...",
"state": "MERGED",
"url": "https://github.com/owner/repo/pull/42",
"author": "username",
"createdAt": "2025-01-15T10:30:00Z",
"mergedAt": "2025-01-16T14:20:00Z",
"baseRef": "main",
"headRef": "feature/new-feature",
"labels": ["enhancement", "ready-for-review"],
"reviews": [
{
"author": "reviewer1",
"state": "APPROVED",
"submittedAt": "2025-01-16T12:00:00Z"
},
{
"author": "reviewer2",
"state": "CHANGES_REQUESTED",
"submittedAt": "2025-01-16T13:00:00Z"
}
]
}
Response Fields
number: PR numbertitle: PR titlebody: PR description/body textstate: PR state (OPEN,CLOSED,MERGED)url: GitHub URL to the PRauthor: PR author usernamecreatedAt: Creation timestamp (ISO 8601)mergedAt: Merge timestamp (ISO 8601),nullif not mergedbaseRef: Target branch nameheadRef: Source branch namelabels: Array of label namesreviews: Array of review objects withauthor,state, andsubmittedAt
How It Works
The server uses the GitHub CLI (gh) to:
-
Extract PR number from commits:
- Searches PRs containing the commit hash
- Parses merge commit messages (
Merge pull request #123) - Parses squash commit messages (
(#123))
-
Retrieve PR details:
- Fetches comprehensive PR information via
gh pr view - Includes reviews, labels, and metadata
- Fetches comprehensive PR information via
-
Auto-detect repository:
- Reads
git remote get-url originfrom the working directory - Extracts
owner/repoformat from the remote URL
- Reads
Development
Setup
npm install
npm run build
Testing
For local testing:
-
Build the project:
npm run build -
Configure your MCP client to use the local build (see Local Development section above)
-
Test with an MCP Inspector or client
Development Scripts
npm run build: Compile TypeScript to JavaScriptnpm run start: Run the compiled servernpm run dev: Run the server in development mode withtsx
Architecture
src/
└── index.ts # Main server implementation
├── Tool handlers # get_pr tool logic
├── Git utilities # Repository detection
└── GitHub CLI # PR extraction and details
License
ISC
Contributing
Contributions welcome! Please read the contributing guidelines and submit a PR.
Related Projects
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。