Backlog MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BACKLOG_DOMAIN | Yes | Your Backlog domain (e.g., your-domain.backlog.com) | |
| BACKLOG_API_KEY | Yes | Your Backlog API key |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_spaceB | Returns information about the Backlog space |
| get_space_activitiesC | Returns list of space activities |
| get_usersB | Returns list of users in the Backlog space |
| get_user_stars_countB | Returns the count of stars received by a user |
| get_myselfB | Returns information about the authenticated user |
| get_user_recent_updatesC | Returns recent updates (activities) for a specific user |
| get_project_listC | Returns list of projects |
| add_projectC | Creates a new project |
| get_projectC | Returns information about a specific project |
| get_project_usersC | Returns list of users in a specific project |
| update_projectC | Updates an existing project |
| get_issueC | Returns information about a specific issue |
| get_issuesC | Returns list of issues |
| count_issuesC | Returns count of issues |
| add_issueC | Creates a new issue in the specified project. |
| update_issueC | Updates an existing issue |
| delete_issueC | Deletes an issue |
| get_issue_commentsC | Returns list of comments for an issue |
| add_issue_commentC | Adds a comment to an issue |
| update_issue_commentC | Updates a comment on an issue |
| get_related_issuesC | Returns list of issues related to a specific issue |
| add_related_issueC | Relates an issue to another issue |
| remove_related_issueB | Removes the relation between an issue and a related issue |
| get_prioritiesC | Returns list of priorities |
| get_categoriesB | Returns list of categories for a project |
| add_categoryC | Creates a new category for a project |
| get_custom_fieldsB | Returns list of custom fields for a project |
| get_issue_typesC | Returns list of issue types for a project |
| get_resolutionsB | Returns list of issue resolutions |
| get_watching_list_itemsC | Returns list of watching items for a user |
| get_watching_list_countC | Returns count of watching items for a user |
| add_watchingC | Adds a new watch to an issue |
| update_watchingC | Updates an existing watch note |
| delete_watchingC | Deletes a watch from an issue |
| mark_watching_as_readC | Mark a watch as read |
| get_version_milestone_listC | Returns list of versions/milestones in the Backlog space |
| add_version_milestoneC | Creates a new version milestone |
| update_version_milestoneD | Updates an existing version milestone |
| delete_versionC | Deletes a version from a project |
| get_wiki_pagesC | Returns list of Wiki pages |
| get_wikis_countB | Returns count of wiki pages in a project |
| get_wikiC | Returns information about a specific wiki page |
| add_wikiC | Creates a new wiki page |
| update_wikiC | Updates an existing wiki page |
| get_git_repositoriesB | Returns list of Git repositories for a project |
| get_git_repositoryC | Returns information about a specific Git repository |
| get_pull_requestsC | Returns list of pull requests for a repository |
| get_pull_requests_countB | Returns count of pull requests for a repository |
| get_pull_requestC | Returns information about a specific pull request |
| add_pull_requestC | Creates a new pull request |
| update_pull_requestC | Updates an existing pull request |
| get_pull_request_commentsC | Returns list of comments for a pull request |
| add_pull_request_commentA | Adds a comment to a pull request |
| update_pull_request_commentC | Updates a comment on a pull request |
| get_documentsC | Gets a list of documents in a project. |
| get_document_treeC | Gets the document tree of a project. |
| get_documentA | Gets information about a document. The content is returned as plain text in |
| get_document_commentsB | Returns list of comments (with their replies) for a document. |
| add_documentC | Adds a new document to the specified project. |
| get_notificationsC | Returns list of notifications |
| count_notificationsC | Returns count of notifications |
| reset_unread_notification_countC | Reset unread notification count |
| mark_notification_as_readC | Mark a notification as read |
| get_issue_attachmentA | Downloads one attachment of an issue. Returns it as MCP image or embedded resource content by default, or as base64 in a JSON object with |
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 64 tools
Most tools clearly target a distinct resource and action, such as get_issue vs. add_issue_comment vs. get_pull_request_comments. A few boundaries could still be confused, especially the mixed count/list tools and version/milestone operations like get_version_milestone_list vs. delete_version.
The dominant pattern is verb_noun, but counting tools are inconsistent: count_issues, count_notifications, get_pull_requests_count, get_wikis_count, and get_watching_list_count all use different structures. There are also singular/plural mismatches such as get_git_repositories vs. get_git_repository and delete_version vs. the version_milestone naming elsewhere.
64 tools is excessive for an MCP server even given Backlog's broad surface area. The set includes many narrow list/count variants, and the cognitive load is high for an agent selecting among them.
Core issue workflows are well covered, including CRUD, comments, related issues, watching, wiki, pull requests, and documents. However, notable gaps remain: documents lack update/delete and comment creation, several metadata resources are read-only, and wiki/project/pull-request deletion or merge operations are absent.