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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
E2B
Using MCP to run code via e2b.