Backlog MCP server

The Backlog MCP Server is an implementation that integrates with the Backlog API, allowing Claude to interact with your Backlog projects, issues, and wikis through the Model Context Protocol (MCP). This server acts as a bridge between Claude and your Backlog workspace.

Available Tools

The server provides access to several Backlog API endpoints through the following tools:

Project Management

• backlog_get_projects: Fetch projects with pagination and filtering
• backlog_get_project: Retrieve a specific project by ID or key

Issue Tracking

• backlog_get_issues: Fetch issues with pagination and filtering
• backlog_get_issue: Retrieve a specific issue by ID or key
• backlog_add_issue: Create a new issue
• backlog_update_issue: Update an existing issue
• backlog_delete_issue: Delete an issue by ID or key

Wiki Management

• backlog_get_wikis: Search wikis by keyword
• backlog_get_wiki: Retrieve a specific wiki by ID or key
• backlog_add_wiki: Create a new wiki
• backlog_update_wiki: Update an existing wiki
• backlog_delete_wiki: Delete a wiki by ID or key

Setting Up

Getting an API Key

Before using the server, you'll need:

1. A Backlog account (sign up at https://backlog.com)
2. A plan (free plan available at https://registerjp.backlog.com/trial/with-new-account/plan/11)
3. An API key from your individual settings (see: https://support-ja.backlog.com/hc/ja/articles/360035641754-API%E3%81%AE%E8%A8%AD%E5%AE%9A)

Required Environment Variables

The server requires these environment variables:

• BACKLOG_API_KEY: Your Backlog API key
• BACKLOG_SPACE_ID: Your Backlog space ID

Optional:

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

Installation and Usage

Using with Claude Desktop

You can add the Backlog MCP Server to your Claude Desktop configuration in two ways:

Using NPX

Add this to your claude_desktop_config.json:

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

Using Docker

If you prefer Docker, add this to your configuration:

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

Make sure to replace the placeholders with your actual API key and space ID values.

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.