home / mcp / backlog mcp server

Backlog MCP Server

Provides an MCP bridge to Backlog APIs for projects, issues, wikis, Git, and notifications.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "nulab-backlog-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "--pull",
        "always",
        "-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"
      }
    }
  }
}

You can run a Backlog MCP Server to interact with the Backlog API through AI agents, enabling project management, issue handling, wiki access, Git operations, and more via a single, configurable bridge.

How to use

Configure an MCP client to connect to one or more MCP server endpoints. You can run the server via Docker, use npx for a quick start, or start a local Node.js instance for development. Choose the method that fits your workflow, then enable the desired toolsets to enable only the capabilities you need.

How to install

Prerequisites you need before starting: Docker, Node.js, or a capable npm/npx setup, and a Backlog account with API access.

Option 1: Install via Docker. Use the following MCP configuration snippet to run the server in a container.

{
  "mcpServers": {
    "backlog": {
      "command": "docker",
      "args": [
        "run",
        "--pull",
        "always",
        "-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"
      }
    }
  }
}

Option 2: Install via npx

You can start quickly with npx without cloning the repository.

Use this MCP configuration in your client setup.

{
  "mcpServers": {
    "backlog": {
      "command": "npx",
      "args": ["backlog-mcp-server"],
      "env": {
        "BACKLOG_DOMAIN": "your-domain.backlog.com",
        "BACKLOG_API_KEY": "your-api-key"
      }
    }
  }
}

Option 3: Manual Setup (Node.js)

If you prefer a local development setup, clone the repository, install dependencies, and run the server locally.

git clone https://github.com/nulab/backlog-mcp-server.git
cd backlog-mcp-server
npm install
npm run build

Create a runtime configuration to start locally from the built index. The following example shows how to point to a local build and seed the required environment values.

{
  "mcpServers": {
    "backlog": {
      "command": "node",
      "args": ["your-repository-location/build/index.js"],
      "env": {
        "BACKLOG_DOMAIN": "your-domain.backlog.com",
        "BACKLOG_API_KEY": "your-api-key"
      }
    }
  }
}

Available tools

space

Tools for managing Backlog space settings and general information

project

Tools for managing projects, categories, custom fields, and issue types

issue

Tools for managing issues, their comments, and related items like priorities and categories

wiki

Tools for managing wiki pages

git

Tools for managing Git repositories and pull requests

notifications

Tools for managing user notifications

document

Tools for viewing and managing documents within Backlog