MCP Backlog Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| readA | Read-only access to backlog items - list and view backlog work items |
| writeC | Write access to backlog management - create, amend, and list backlog work items |
| doneC | Mark backlog items as complete with optional summary - done operation and list |
| ticket-readA | Read-only access to backlog tickets - list and filter tickets for a backlog item |
| ticket-writeC | Write access to backlog tickets - create and update tickets for backlog items |
| ticket-doneC | Mark backlog tickets as complete with dependency validation |
| pruneC | Prune completed/done backlog items - remove old archived items from COMPLETED_Backlog |
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 7 tools
Tools are mostly distinct, but 'done' and 'ticket-done' could confuse an agent as both mark items complete; similarly 'read' vs 'ticket-read' and 'write' vs 'ticket-write' are pairs with overlapping purposes, though descriptions clarify the backlog vs ticket context.
Naming is inconsistent: plain verbs (done, prune, read, write) and noun-verb with hyphen (ticket-done, ticket-read, ticket-write) mix styles. The verb placement also varies (verb-first vs noun-first).
Seven tools is a reasonable number for managing backlog items and tickets, covering necessary operations without excess or deficiency.
The tool set covers core CRUD-like operations for both backlog items and tickets, including creation, reading, updating, completing, and pruning. Minor gaps include lack of explicit delete for backlog items or tickets (beyond pruning), but these are not severe.