commit-to-pr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | The logging level for the server (e.g., 'debug', 'info', 'warn', 'error'). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.