Backlog MCP Server

Name: Backlog MCP Server
Author: MCP-Mirror

@MCP-Mirror

代码仓库

关于 Backlog MCP Server

Mirror of

#backlog #mcp-server #project-management

基本信息

分类

其他

许可证

MIT license

运行时

node

传输方式

stdio

发布者

MCP-Mirror

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "backlog": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "BACKLOG_DOMAIN",
        "-e",
        "BACKLOG_API_KEY",
        "ghcr.io/nulab/backlog-mcp-server"
      ],
      "env": {
        "BACKLOG_DOMAIN": "your-domain.backlog.com",
        "BACKLOG_API_KEY": "your-api-key"
      }
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Backlog MCP Server?

A Model Context Protocol (MCP) server that enables AI agents like Claude Desktop, Cline, and Cursor to interact with the Backlog API. It provides tools for managing projects, issues, wiki pages, Git repositories, pull requests, notifications, and watching items.

How to use Backlog MCP Server?

Configure the server in your MCP‑compatible client using Docker (recommended) or a manual Node.js installation. Set environment variables BACKLOG_DOMAIN (your Backlog domain) and BACKLOG_API_KEY (your API key). Optional variables MAX_TOKENS and OPTIMIZE_RESPONSE control response size and field selection.

Key features of Backlog MCP Server

Project management (CRUD operations)
Issue tracking with comments
Wiki page management
Git repository management
Pull request management with comments
Notification and watching list management
GraphQL‑style field selection for optimized responses
Configurable token limiting for large responses

Use cases of Backlog MCP Server

List all projects and their details through natural language
Create, update, or delete issues with priority and type
Retrieve and filter issues by project or status
Manage pull requests, including creating and commenting
Fetch watching items and notification counts

FAQ from Backlog MCP Server

What are the dependencies and runtime requirements?

The server runs via Docker or Node.js (after building from source). You need a Backlog account with API access and a valid API key. Docker is the simplest deployment method.

Where does my data live?

All data remains in your Backlog space. The server is stateless; it only makes API calls to Backlog and does not store any data locally.

How can I limit response size or select only specific fields?

Set MAX_TOKENS (default 50 000) to cap token usage, and set OPTIMIZE_RESPONSE=true to enable GraphQL‑style field selection in your queries.

Can I customize tool descriptions or use a different language?

Yes. Create a .backlog-mcp-serverrc.json file in your home directory, or set environment variables (e.g., BACKLOG_MCP_TOOL_ADD_ISSUE_COMMENT_DESCRIPTION). A Japanese translation template is provided.