Overview
What is mCP-backlog-server?
mcp-backlog-server is a TypeScript-based server that integrates Backlog project management with the Model Context Protocol (MCP). It provides resources, tools, and prompts to access and interact with Backlog data, ideal for users who want to manage Backlog projects through MCP-compatible clients like Claude Desktop.
How to use mcp-backlog-server?
Install dependencies with npm install, then build with npm run build. Configure the server in your Claude Desktop config file (claude_desktop_config.json) by specifying the path to the build output and setting two environment variables: BACKLOG_API_KEY and BACKLOG_SPACE_URL.
Key features of mcp-backlog-server
- Access Backlog projects via structured
backlog://project/[id]resources - Retrieve user, space, project, issue, and wiki information
- Filter and paginate issue lists by status, assignee, and more
- Add comments to issues and read their details
- Summarize recent projects and analyze usage patterns
- Summarize project wiki pages with a dedicated prompt
Use cases of mcp-backlog-server
- Summarize recently viewed Backlog projects for a quick overview
- Analyze Backlog usage patterns based on user, space, and project data
- Retrieve and update project issues and wiki pages programmatically
- Add comments to issues directly from an MCP client
- Generate structured summaries of wiki pages for a project
FAQ from mcp-backlog-server
What prerequisites are needed to run the server?
You need a Backlog account with API access and set the BACKLOG_API_KEY and BACKLOG_SPACE_URL environment variables.
How is the server configured in Claude Desktop?
Add a JSON entry in claude_desktop_config.json with the server command pointing to the build file and the required environment variables.
How can I debug the server?
Use the MCP Inspector by running npm run inspector, which provides a browser-based debugging tool.
Where does the data come from?
All data is fetched from the Backlog API using your API key and space URL; no local storage is used.
What transport does the server use?
The server communicates via standard input/output (stdio) as typical for MCP servers.
