patchwork-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PATCHWORK_URL | No | Base URL of the Patchwork instance | https://patchwork.kernel.org |
| PATCHWORK_API_VERSION | No | REST API version segment | 1.2 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List Patchwork projects available on the configured instance. Returns id, link_name (used as ?project= filter), display name, and list_id. |
| find_by_msgidA | Look up patches and cover letters by Message-Id across all projects. A single Message-Id can appear under multiple projects (e.g. netdevbpf and linux-kselftest). Use this to discover the projects + series ids before drilling in. |
| get_seriesA | Get a series with every patch's state, delegate, and archived flag. Use this after find_by_msgid to see the whole patchset at once. |
| get_patchC | Get a single patch with submitter, delegate, state, tags, and check summary. |
| get_checksA | Get CI check results for a patch (checkpatch, build_*, sashiko-*, contest, ...). Pair with get_patch's check_summary to triage failing series quickly. |
| get_commentsB | Get the comment thread on a cover letter or a patch, time-ordered. |
| recent_seriesC | List recent cover letters on a project, optionally filtered by submitter. With collapse_revisions=True, older revisions of the same series name are dropped so you only see the latest version of each topic. |
| search_patchesA | Search patches by name substring with optional project/state/submitter filters. |
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 8 tools
Each tool targets a distinct operation: lookup by message ID, get patch details, get series, get comments, get checks, list projects, list recent series, and search patches. No two tools have overlapping purposes.
Tools mostly follow a verb_object pattern with underscores (e.g., get_patch, list_projects). 'recent_series' deviates slightly as adjective_object, but overall style is consistent and clear.
With 8 tools, the server covers core interactions without being too sparse or overwhelming. Each tool serves a clear need within the Patchwork domain.
The set covers essential read operations: project listing, patch/series retrieval, comments, checks, and search. Missing creation or modification tools, but that aligns with a read-focused MCP server.