Server facts
backlog-mcp-server
Project
- Author
- tmhr1850
- Repository
- github.com/tmhr1850/backlog-mcp-server
- License
- MIT license
- Category
- Productivity
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 11
- Last commit
- Data as of
Tags
- api server
- backlog
- project management
Overview
Backlog work starts with finding the right space, project, and issue. The supplied tool catalog includes getSpaces and getProjects for that context, followed by getIssues for project issue lists and getIssue for an individual record. createIssue adds work to a project, while getWikiPages, getUsers, and getWebhooks expose additional lists. Together, these tools serve Backlog users who want project information and issue creation available through an MCP connection rather than treating every interaction as a separate API task.
The README describes further issue workflows: updating existing records, adding comments, and searching by keyword with an optional project scope. Its issue-list options include pagination and sorting by creation or update time. Creation and update inputs cover details such as descriptions, assignees, priorities, and dates; updates also accept a status. Configuration uses a Backlog domain and API key, with a Claude Desktop setup example provided. The project runs on Node, communicates over stdio, and carries an MIT license. The README’s additional workflows are documented separately from the supplied tool catalog.
backlog-mcp-server setup notes
- backlog-mcp-server records stdio only; confirm a network transport upstream before planning remote access.