MCP Backlog Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rwese/mcp-backlog'
If you have feedback or need assistance with the MCP directory API, please join our Discord server