Backlog MCP Server for Claude
Manage Backlog projects from Claude — create and update issues, comment on tickets, manage wiki pages, review pull requests, and navigate your Nulab Backlog space — with the official Backlog MCP server supporting stdio and HTTP transports.
Open the source and read safety notes before installing.
Safety notes
- Tools can create, update, and delete projects, issues, wikis, and pull requests — changes affect your live Backlog space.
- Use `ENABLE_TOOLSETS` to restrict which tool groups are available if you only need read access.
Privacy notes
- Issue content, comments, wiki pages, pull request details, and user information from your Backlog space are surfaced in Claude's context.
- Your `BACKLOG_API_KEY` grants account-level Backlog access — keep it in the MCP config env and never commit it to version control.
Prerequisites
- A Backlog account on backlog.com or your Backlog.jp/enterprise space.
- A Backlog API key: Personal Settings → API → Generate API Key.
- Node.js with `npx` available.
- An MCP client such as Claude Code or Claude Desktop.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 5 minutes
- Difficulty
- beginner
- Website
- https://backlog.com
Full copyable content
{
"mcpServers": {
"backlog": {
"command": "npx",
"args": ["backlog-mcp-server"],
"env": {
"BACKLOG_DOMAIN": "yourspace.backlog.com",
"BACKLOG_API_KEY": "<your-api-key>"
}
}
}
}About this resource
Overview
The Backlog MCP Server is the official Model Context Protocol server from Nulab for
Backlog, the project management and collaboration platform popular in
Japan and across Asia. It provides tools for managing projects, issues, wikis, Git repositories,
pull requests, notifications, and documents. Both stdio (local npx) and HTTP transports are
supported. Licensed under MIT.
Key capabilities
- Issues — create, read, update, and delete issues; add comments.
- Projects — manage projects and issue types.
- Wikis — create and read wiki pages.
- Git — repository management, pull requests, PR comments.
- Notifications — list, mark read/unread, check unread counts.
- Documents — navigate document trees and listings.
- Space info — retrieve space settings, user list, and authenticated user info.
How it compares
| Server | Issues | Wiki | Pull requests | Git | Notes |
|---|---|---|---|---|---|
| Backlog MCP | Yes | Yes | Yes | Yes | Official Nulab |
| Jira MCP | Yes | Yes (Confluence) | No | No | Atlassian |
| Linear MCP | Yes (issues) | No | No | No | Engineering-focused |
| Asana MCP | Yes (tasks) | No | No | No | Task management |
Backlog is the only project management MCP that integrates issue tracking, wiki documentation, and Git pull request review in a single server.
Installation
Claude Code
claude mcp add backlog \
-e BACKLOG_DOMAIN=yourspace.backlog.com \
-e BACKLOG_API_KEY=<your-api-key> \
-- npx backlog-mcp-server
Generate your API key at: Personal Settings → API → Generate API Key in your Backlog account.
Claude Desktop
{
"mcpServers": {
"backlog": {
"command": "npx",
"args": ["backlog-mcp-server"],
"env": {
"BACKLOG_DOMAIN": "yourspace.backlog.com",
"BACKLOG_API_KEY": "<your-api-key>"
}
}
}
}
Configuration options
| Env var | Default | Purpose |
|---|---|---|
BACKLOG_DOMAIN |
— | Required. Your space domain (e.g. yourspace.backlog.com) |
BACKLOG_API_KEY |
— | Required. API key from Personal Settings |
BACKLOG_OAUTH_CLIENT_ID |
— | Optional OAuth 2.0 client ID |
BACKLOG_OAUTH_CLIENT_SECRET |
— | Optional OAuth 2.0 client secret |
MAX_TOKENS |
50000 |
Response token limit |
ENABLE_TOOLSETS |
all | Comma-separated toolsets to enable |
MCP_TRANSPORT |
stdio |
stdio or http |
Requirements
- A Backlog account (backlog.com, backlog.jp, or self-hosted).
- Node.js (for
npx). - An MCP client (Claude Code or Claude Desktop).
Security
BACKLOG_API_KEYgrants full account access — keep it in the MCP config env.- Use
ENABLE_TOOLSETSto restrict to read-only toolsets in team deployments.
Source Verification Notes
Verified on 2026-06-18:
- Official repository
nulab/backlog-mcp-server(MIT) documentsnpx backlog-mcp-server,BACKLOG_DOMAIN/BACKLOG_API_KEYconfiguration, all tool categories (Project, Issue, Wiki, Git, Notifications, Document, Space), OAuth 2.0 support, response token limits, toolset filtering, and HTTP transport mode. - Claude Code MCP documentation at
code.claude.com/docs/en/mcpdescribes the stdio connector pattern used above.
Source citations
Add this badge to your README
How it compares
Backlog MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Backlog MCP Server for Claude Manage Backlog projects from Claude — create and update issues, comment on tickets, manage wiki pages, review pull requests, and navigate your Nulab Backlog space — with the official Backlog MCP server supporting stdio and HTTP transports. Open dossier | Taskade MCP Server for Claude Connect Claude to Taskade — manage workspaces, projects, tasks, and AI agents — with the official Taskade MCP server, covering 57 tools for the full Taskade platform including projects, tasks, AI agent conversations, media, and templates. Open dossier | Trello MCP Server MCP server for Trello boards, cards, lists, comments, checklists, attachments, labels, board activity, workspace selection, and rate-limited Trello API automation from Claude. Open dossier | ConfigCat MCP Server for Claude Manage ConfigCat feature flags from Claude — create, update, and delete flags and targeting rules, manage environments, find and clean up stale flags, and audit change history — with the official ConfigCat MCP server and its 52 tools for the full ConfigCat Management API. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Nulab | Taskade | Jarad DeLorenzo | ConfigCat |
| Added | 2026-06-18 | 2026-06-18 | 2026-06-06 | 2026-06-18 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓Tools can create, update, and delete projects, issues, wikis, and pull requests — changes affect your live Backlog space. Use `ENABLE_TOOLSETS` to restrict which tool groups are available if you only need read access. | ✓Tools can create, update, and delete projects, tasks, and AI agents in your Taskade account — changes affect live data. AI agent tools (`agentCreate`, `agentUpdate`, `agentDelete`) modify live agent configurations — review before executing. | ✓Trello MCP Server can create, read, update, move, archive, and delete board data depending on token permissions and requested tools. Card, checklist, label, due-date, start-date, comment, attachment, board, list, workspace, and active-board changes can affect real team workflows. File attachments are added from URLs; review source URLs and destination cards before allowing an agent to attach files. Use `TRELLO_ALLOWED_WORKSPACES` to limit workspace access, especially when a token can see personal, client, or production boards. Require confirmation before creating boards, adding attachments, deleting or archiving cards, changing due dates, moving cards between lists, or posting comments on behalf of a user. | ✓Tools can create, update, and delete feature flags, targeting rules, environments, and segments — changes affect live feature flag configuration. Use `list-staleflags` before deleting flags to identify zombie flags and avoid breaking active SDKs. |
| Privacy notes | ✓Issue content, comments, wiki pages, pull request details, and user information from your Backlog space are surfaced in Claude's context. Your `BACKLOG_API_KEY` grants account-level Backlog access — keep it in the MCP config env and never commit it to version control. | ✓Workspace names, project content, task details, and AI agent conversation history from your Taskade account are surfaced in Claude's context. Your `TASKADE_API_KEY` grants full account access — keep it in the MCP config env and never commit it to version control. | ✓Trello API keys, tokens, board IDs, workspace IDs, card IDs, member names, labels, comments, checklists, attachments, due dates, and activity logs can be exposed to the MCP client. Active board and workspace selections may persist locally in Trello MCP configuration. Card descriptions, comments, attachments, and activity histories can contain private customer, roadmap, incident, or operational data. Proxy settings, Trello credentials, and workspace allowlists should be kept out of shared MCP configs, logs, screenshots, and transcripts. Response previews reduce some large card-description exposure, but full-card and activity tools can still return sensitive Trello content. | ✓Feature flag configurations, targeting rules, audience segments, SDK keys, and audit log entries from your ConfigCat account are surfaced in Claude's context. `CONFIGCAT_API_USER` and `CONFIGCAT_API_PASS` are Management API credentials — keep them in the MCP config env and never commit them to version control. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.