Backlog MCP Server
The Backlog MCP Server integrates with the Backlog API for comprehensive project management:
Project Management: Retrieve projects with pagination and filtering, and access specific project details using ID or key.
Issue Management: Retrieve, create, update, and delete issues with support for extensive filtering options by keyword, status, assignee, etc. Includes sorting and pagination capabilities.
Wiki Management: Retrieve, create, update, and delete wiki pages with keyword search functionality and email notification options.
Configuration: Requires Backlog API key and space ID, with optional base URL customization.
Integration: Can be used with Claude Desktop via NPX or Docker, configured through environment variables.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Backlog MCP Server show me the open issues in project ABC-123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Official Backlog MCP server launched!
This repository will be changed visible.
https://nulab.com/ja/blog/backlog/released-backlog-mcp-server/
Backlog MCP Server
An MCP server implementation that integrates the Backlog API.
Tools
Project API
backlog_get_projects
Execute projects get with pagination and filtering
backlog_get_project
Execute project gets with project id or key
Issue API
backlog_get_issues
Execute issues get with pagination and filtering
backlog_get_issue
Execute issue gets with issue id or key
backlog_add_issue
Execute issue add with issue data
backlog_update_issue
Execute issue update with issue data
backlog_delete_issue
Execute issue delete with issue id or key
Wiki API
backlog_get_wikis
Execute wikis get with keyword
backlog_get_wiki
Execute wiki gets with wiki id or key
backlog_add_wiki
Execute wiki add with wiki data
backlog_update_wiki
Execute wiki update with wiki data
backlog_delete_wiki
Execute wiki delete with wiki id or key
Related MCP server: MCP Server Linear
Configuration
Getting an API Key
Sign up for a Backlog
Choose a plan (Free plan available here)
Generate your API key from the individual settings help
Environment Variables
This server requires the following environment variables:
Required:
BACKLOG_API_KEY: Your Backlog API keyBACKLOG_SPACE_ID: Your Backlog space ID
Optional:
BACKLOG_BASE_URL: Your Backlog base URL (default:https://{your-space-id}.backlog.com/api/v2)
Usage with Claude Desktop
Add this to your claude_desktop_config.json:
NPX
{
"mcpServers": {
"backlog": {
"command": "npx",
"args": [
"-y",
"backlog-mcp-server"
],
"env": {
"BACKLOG_API_KEY": "YOUR_API_KEY_HERE",
"BACKLOG_SPACE_ID": "YOUR_SPACE_ID_HERE"
}
}
}
}Docker
{
"mcpServers": {
"backlog": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"BACKLOG_API_KEY=YOUR_API_KEY_HERE",
"-e",
"BACKLOG_SPACE_ID=YOUR_SPACE_ID_HERE",
"mcp/backlog"
],
"env": {
"BACKLOG_API_KEY": "YOUR_API_KEY_HERE",
"BACKLOG_SPACE_ID": "YOUR_SPACE_ID_HERE"
}
}
}
}Development
Installation
npm installBuild
npm run buildDebug
npm run debugRunning Tests
T.B.D
Docker Build
docker build -t mcp/backlog -f Dockerfile .Extending the Server
To add new tools:
Define a new Zod schema in
src/core/schema.tsAdd a new tool definition in
src/tools/toolDefinitions.tsand include it inALL_TOOLSCreate a new handler in
src/tools/handlers.tsand register it intoolHandlersImplement business logic in a service in the
src/services/directory
License
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
Available Tools
12 toolsbacklog_add_issueC
Add an issue using the Backlog Issue API.
Inputs: issueTypeId (required), priorityId (required), projectId (required), summary (required), +9 more.
backlog_add_wikiC
Add an wiki using the Backlog Wiki API.
Inputs: content (required), name (required), projectId (required), mailNotify.
backlog_delete_issueC
Delete an issue using the Backlog Issue API.
Inputs: issueIdOrKey (required).
backlog_delete_wikiC
Delete an wiki using the Backlog Wiki API.
Inputs: wikiId (required), mailNotify.
backlog_get_issueC
Performs an issue get using the Backlog Issue API.
Inputs: issueIdOrKey (required).
backlog_get_issuesC
Performs list issue get using the Backlog Issues API. Supports pagination, content filtering. Maximum 20 results per request, with offset for pagination.
Inputs: assigneeId, count, createdSince, createdUntil, +7 more.
backlog_get_projectC
Performs an project get using the Backlog Project get API.
Inputs: projectIdOrKey (required).
backlog_get_projectsB
Performs list project get using the Backlog Projects get API. Supports pagination, content filtering. Maximum 20 results per request, with offset for pagination.
Inputs: all, archived.
backlog_get_wikiC
Performs an wiki get using the Backlog Wiki API.
Inputs: wikiId (required).
backlog_get_wikisC
Performs list wikis get using the Backlog Wiki API
Inputs: projectIdOrKey (required), keywords.
backlog_update_issueB
Update an issue using the Backlog Issue API.
Inputs: issueIdOrKey (required), actualHours, assigneeId, attachmentId, +14 more.
backlog_update_wikiC
Update an wiki using the Backlog Wiki API.
Inputs: wikiId (required), content, mailNotify, name.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized by resource type (issue, wiki, project) and action (add, delete, get, update), making it easy for an agent to select the correct one. There's no overlap in functionality between tools.
All tool names follow a perfect and consistent pattern: 'backlog_' prefix + verb (add, delete, get, update) + singular/plural noun (issue, wiki, project). The naming is systematic and predictable throughout the entire set.
12 tools is well-scoped for a Backlog server covering issues, wikis, and projects. Each tool earns its place with clear CRUD operations for each resource type, providing comprehensive coverage without being overwhelming.
The tool surface provides complete CRUD/lifecycle coverage for all three resource types (issues, wikis, projects). There are no obvious gaps - each resource has add, delete, get (both single and list), and update operations where applicable.
Related MCP Connectors
A MCP server built for developers enabling Git based project management with project and personal…
MCP server for generating rough-draft project plans from natural-language prompts.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Related MCP Servers
- FlicenseCqualityDmaintenanceThis is an MCP server that facilitates building tools for interacting with various APIs and workflows, supporting Python-based development with potential for customizable prompts and user configurations.1-
- AlicenseNot gradedqualityFmaintenanceAn MCP server that provides tools for interacting with Linear issue tracking system, currently supporting issue search with plans to expand to issue creation, updates, comments, and project management.2,467 npm1MIT
- AlicenseCqualityBmaintenanceA Model Context Protocol server that enables AI assistants to interact with Linear project management systems, allowing users to retrieve, create, and update issues, projects, and teams through natural language.19885,521 npm149MIT
- AlicenseCqualityDmaintenanceAn MCP server that connects to Backlog API, providing functionality to search, retrieve, and update issues through natural language commands.410,810 npm6MIT