ProofHub MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROOFHUB_API_KEY | Yes | Your ProofHub API key | |
| PROOFHUB_API_BASE | No | Base URL of the ProofHub API, e.g., https://company.proofhub.com/api/v3 |
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 |
|---|---|
| proofhub_parse_urlA | Parse a ProofHub task URL and return the project ID, list ID, and task ID embedded in it. Use this as the first step before calling other ProofHub tools. |
| proofhub_get_taskC | Fetch full task details (title, description, stage, custom fields, assignees) from ProofHub. |
| proofhub_get_commentsC | Fetch all comments on a ProofHub task, including their full text. |
| proofhub_get_task_with_bug_linksB | One-shot tool: given a ProofHub task URL (or IDs), fetches the task description AND all comments, then extracts any bug-tracker links (Jira, Linear, GitHub Issues, GitLab, YouTrack, ClickUp, Asana, etc.) found in any of those texts. Returns the task data plus a deduplicated list of bug links. |
| proofhub_create_commentC | Post a new comment on a ProofHub task. |
| proofhub_get_task_historyB | Fetch the activity history of a ProofHub task (stage changes, edits, etc.). |
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 6 tools
Each tool has a clearly distinct purpose: creating comments, fetching comments, getting task details, getting task history, a composite bug-link extractor, and a URL parser. No overlap.
All tools use the 'proofhub_' prefix followed by consistent snake_case verb_noun patterns (e.g., create_comment, get_task, parse_url). Naming is uniform and predictable.
With 6 tools, the server is well-scoped for interacting with ProofHub tasks. Each tool serves a clear purpose without bloat or deficiency.
The tool set covers creation, reading, and composite extraction, but lacks update, delete, and list operations for tasks and comments. This creates notable gaps for full lifecycle management.