pickfix-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PICKFIX_HOME | No | Set to use another directory for PickFix files (default is ~/.pickfix). | |
| PICKFIX_EXTENSION_IDS | No | Allows extra extension ids, for unpacked builds made without the PickFix key. Comma-separated list of ids. |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| experimental | {
"claude/channel": {}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pickfix_statusA | Show this session's Pickfix link: repository, WebSocket port (or why there is none), and how many feedback batches are in each state. |
| pickfix_list_batchesA | List the feedback batches the Pickfix extension sent for this repository. By default shows queued and working batches. |
| pickfix_claim_batchA | Claim a feedback batch before changing any code for it, and receive its items: the reviewer's requests, where each element or region lives in the code, screenshots of the current state and any reference images showing the desired look. Without batchId, claims the oldest queued batch. A batch can be claimed only once across all sessions. |
| pickfix_reportA | Report the outcome of a batch you claimed. Always call this when you finish, including when you could only partly fix it or not at all; the reviewer sees the summary in the extension. |
| pickfix_importA | Add a batch exported from the Pickfix extension as a JSON file to this repository's queue, then claim it with pickfix_claim_batch. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| fix | Fix UI feedback that the Pickfix browser extension queued for this repository. Use when the user mentions Pickfix feedback, queued UI feedback or a batch id to handle. Do not use for bug reports or UI changes the user describes directly. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool maps to a distinct step in the feedback-batch lifecycle: status (session overview), list_batches (enumerate), claim_batch (acquire), report (close out), and import (ingest external). Status and list_batches both surface batch info, but one is session/connection health while the other enumerates batches, so boundaries stay clear.
All five tools use the same pickfix_ prefix followed by a clear verb or verb_noun (status, list_batches, claim_batch, report, import). The pattern is predictable and readable throughout.
Five tools is well-scoped for a focused claim/work/report workflow, with each tool earning its place. No redundancy or filler.
The surface covers the core lifecycle: inspect session, list batches, claim, receive items, report outcome, plus importing external batches. A release/unclaim path (returning a claimed batch to the queue) is missing, which could be a dead end if a claim is abandoned, but agents can otherwise work around it.