commit-to-pr-mcp
Automatically detects repository information and identifies git references such as commit hashes or branch names within local working directories to resolve them into pull requests.
Retrieves comprehensive GitHub pull request data, including titles, descriptions, labels, and review history, by using the GitHub CLI to resolve commit hashes or PR numbers.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@commit-to-pr-mcp show me the pull request details for commit 8f2a1b"
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.
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
Related MCP server: GitHub MCP Server
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"
]
}
}
}Use the Claude Code CLI to add the server:
claude mcp add commit-to-pr npx commit-to-pr-mcp@latestAdd 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"]
}
}
}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"]
}
}
}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"]}'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"
]
}
}
}Follow the MCP Servers documentation. Use the standard config above.
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 viewIncludes reviews, labels, and metadata
Auto-detect repository:
Reads
git remote get-url originfrom the working directoryExtracts
owner/repoformat from the remote URL
Development
Setup
npm install
npm run buildTesting
For local testing:
Build the project:
npm run buildConfigure 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 detailsLicense
ISC
Contributing
Contributions welcome! Please read the contributing guidelines and submit a PR.
Related Projects
Available Tools
1 toolget_prA
Get PR details by commit hash or PR number. Extracts PR number from git commits (merge commits, squash commits) and returns full PR details including title, description, author, status, and reviews. Auto-detects repository from working directory.
Inputs: commit, pr_number, repo, cwd.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct as it is the only tool available.
The single tool name 'get_pr' follows a clear verb_noun pattern. With only one tool, naming consistency is inherently perfect as there are no other tools to compare against.
A single tool is too few for most practical server purposes, as it severely limits functionality and scope. While the tool is specific, the server's capability is minimal and likely insufficient for comprehensive workflows.
The server's domain appears to be PR-related operations, but with only a 'get' tool, there are significant gaps. It lacks create, update, delete, or other PR management functions, making the surface incomplete for typical PR workflows.
Maintenance
Related MCP Connectors
An MCP server that gives your AI access to the source code and docs of all public github repos
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
A MCP server built for developers enabling Git based project management with project and personalβ¦
GitHub Copilot MCP: code, repo, PR, workflow tools for AI assistants.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that wraps around the GitHub CLI tool, allowing AI assistants to interact with GitHub repositories through commands for pull requests, issues, and repository operations.22 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to directly manage GitHub repositories, including PRs, issues, and code search, using natural language.MIT
- FlicenseAqualityDmaintenanceA minimal MCP server that exposes a focused set of GitHub PR review tools to AI agents, enabling PR listing, detail retrieval, comment viewing, and thread management.5-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for interacting with the GitHub API, enabling AI assistants to query repositories, pull requests, issues, commits, users, and more.489 npmISC