Backlog MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BACKLOG_API_KEY | Yes | Your Backlog API key | |
| BACKLOG_SPACE_URL | Yes | Your Backlog space URL (e.g. https://your-space.backlog.com) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getProjectsB | Backlogのプロジェクト一覧を取得します |
| searchIssuesC | Backlogの課題を検索します |
| getIssueC | 特定のBacklog課題を取得します |
| updateIssueC | 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 4 tools
Each tool has a clearly distinct purpose: getIssue retrieves a specific issue, getProjects lists projects, searchIssues finds issues based on criteria, and updateIssue modifies an issue. There is no overlap or ambiguity between these functions.
The naming follows a consistent verb_noun pattern (e.g., getIssue, getProjects, searchIssues, updateIssue), with all tools using camelCase. The only minor deviation is that 'getProjects' uses a plural noun while others use singular, but this is still readable and predictable.
With only 4 tools, the set feels thin for a Backlog server, as it lacks essential operations like creating issues or projects, deleting resources, or managing comments. While the tools cover basic retrieval and update, the scope is incomplete for typical issue-tracking workflows.
There are significant gaps in the tool surface for a Backlog server. Missing operations include create_issue, delete_issue, create_project, and update_project, which are core to issue lifecycle management. This will likely cause agent failures when trying to perform full CRUD operations.