Backlog MCP 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getSpacesC | スペース情報の取得 |
| getProjectsB | プロジェクト一覧の取得 |
| getIssuesC | 課題一覧の取得 |
| getIssueC | 特定の課題情報の取得 |
| createIssueC | 課題の追加 |
| getWikiPagesC | Wikiページ一覧の取得 |
| getUsersC | ユーザー一覧の取得 |
| getWebhooksB | Webhook一覧の取得 |
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
Every tool has a clearly distinct purpose targeting different resources: createIssue (create), getIssue (single read), getIssues (list read), getProjects (list), getSpaces (list), getUsers (list), getWebhooks (list), and getWikiPages (list). There is no ambiguity or overlap in functionality.
All tools follow a consistent verb_noun pattern with camelCase: createIssue, getIssue, getIssues, getProjects, getSpaces, getUsers, getWebhooks, and getWikiPages. The naming is predictable and readable throughout.
With 8 tools, the count is well-scoped for a Backlog server, covering core operations like issue management, project listing, and user retrieval. Each tool earns its place without being excessive or insufficient.
The server covers read operations extensively (get for issues, projects, spaces, users, webhooks, wiki pages) and create for issues, but lacks update and delete operations for issues, projects, or other resources. This creates notable gaps in CRUD coverage for the domain.