backlog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BACKLOG_API_KEY | Yes | Your Backlog API key | |
| BACKLOG_BASE_URL | Yes | Your Backlog space URL (e.g., https://yourspace.backlog.com) | |
| BACKLOG_TASKS_DIR | No | Local tasks directory (defaults to .tasks) | .tasks |
| BACKLOG_PROJECT_KEY | Yes | Your project key (e.g., PROJ) | |
| BACKLOG_IGNORE_ISSUE_TYPES | No | Comma-separated list of issue types to ignore (e.g., Bug,Task) |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sync-issuesA | Sync issues from Backlog to local .tasks folder |
| get-issueA | Get details of a specific Backlog issue |
| test-connectionA | Test connection to Backlog API |
| update-issuesC | Update Backlog issues with changes from local task files |
| list-task-filesA | List existing task files in .tasks directory |
| bulk-create-tasksB | Create Backlog issues from local temporary task files in parent folders |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| tasks-directory | List all task files in the .tasks directory |
TDQS
Scored across 6 tools
Each tool has a distinct role: syncing remote-to-local, local-to-remote, fetching a single issue, creating issues in bulk, listing local files, and testing connectivity. Sync-issues and update-issues are closely related as inverse operations, but their descriptions clarify direction. No two tools appear to do the same thing.
Tool names mostly follow a verb-noun pattern: sync-issues, get-issue, update-issues, list-task-files, test-connection. Minor inconsistency exists with get-issue singular versus plural elsewhere, and bulk-create-tasks uses a compound verb prefix. Overall the pattern is predictable and readable.
Six tools is well-scoped for a Backlog-to-local-file synchronization server. Each tool covers a necessary operation without redundancy or bloat. The count feels appropriate for the stated purpose.
The tool set covers the core sync workflow: test connection, read local files, fetch remote issues, push updates, and bulk-create issues from local files. A single-issue create or delete operation is missing, but the bulk-create and update tools cover the main lifecycle needs. Minor gaps exist but agents can likely complete typical workflows.