Home / MCP / Backlog MCP Server

Backlog MCP Server

Provides an MCP server that integrates the Backlog API to manage projects, issues, and wikis.

typescript

3stars

View on GitHub

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
    "mcpServers": {
        "backlog": {
            "command": "npx",
            "args": [
                "-y",
                "backlog-mcp-server"
            ],
            "env": {
                "BACKLOG_API_KEY": "YOUR_API_KEY_HERE",
                "BACKLOG_SPACE_ID": "YOUR_SPACE_ID_HERE",
                "BACKLOG_BASE_URL": "https://{space-id}.backlog.com/api/v2"
            }
        }
    }
}

You set up and run a Backlog MCP Server to access Backlog data through a standardized MCP interface. This server lets you manage projects, issues, and wikis from Backlog via defined actions, so you can build tooling, dashboards, or integrations without writing your own API calls.

How to use

You connect your MCP client to the Backlog MCP Server and perform operations such as listing projects, fetching issues, and managing wikis. Each action maps to a Backlog API capability, enabling you to drive workflows, automate updates, and surface Backlog data in your tools.

How to install

Prerequisites: ensure you have Node.js and npm installed if you plan to build locally. You can also run the server via containerized commands if you prefer Docker.

Step 1: Install dependencies and build the project locally.

npm install
```

```bash
npm run build

Usage with Claude Desktop

Configure the MCP server within Claude Desktop to run as a local process using NPX or Docker. The following configurations show how to start the server and provide required environment credentials.

{
  "mcpServers": {
    "backlog": {
      "command": "npx",
      "args": [
        "-y",
        "backlog-mcp-server"
      ],
      "env": {
        "BACKLOG_API_KEY": "YOUR_API_KEY_HERE",
        "BACKLOG_SPACE_ID": "YOUR_SPACE_ID_HERE"
      }
    }
  }
}

{
  "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"
      }
    }
  }
}

Configuration and environment variables

The server requires authentication and space context from Backlog. Provide these values as environment variables when starting the MCP server.

Required environment variables:

- BACKLOG_API_KEY: Your Backlog API key

- BACKLOG_SPACE_ID: Your Backlog space ID

Optional environment variable:

- BACKLOG_BASE_URL: Your Backlog base URL (default: https://{your-space-id}.backlog.com/api/v2)

Development and testing

For development, you can run in debug mode to inspect requests and responses.

npm run debug

Extending the server

To add new capabilities, extend the server by defining a new schema, adding a tool, implementing a handler, and wiring business logic in services.

Docker build

docker build -t mcp/backlog -f Dockerfile .

Available tools

backlog_get_projects

Execute projects get with pagination and filtering

backlog_get_project

Execute project gets with project id or key

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

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