Skip to main content
Glama
Backlog MCP Server

Backlog MCP Server

by fleagne
CAUTION

Official Backlog MCP server launched!

This repository will be changed visible.

https://nulab.com/ja/blog/backlog/released-backlog-mcp-server/

Backlog MCP Server

An MCP server implementation that integrates the Backlog API.

Tools

Project API

  • backlog_get_projects

    • Execute projects get with pagination and filtering

  • backlog_get_project

    • Execute project gets with project id or key

Issue API

  • 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

Wiki API

  • 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

Related MCP server: MCP Server Linear

Configuration

Getting an API Key

  1. Sign up for a Backlog

  2. Choose a plan (Free plan available here)

  3. Generate your API key from the individual settings help

Environment Variables

This server requires the following environment variables:

  • Required:

    • 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)

Usage with Claude Desktop

Add this to your claude_desktop_config.json:

NPX

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

Docker

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

Development

Installation

npm install

Build

npm run build

Debug

npm run debug

Running Tests

T.B.D

Docker Build

docker build -t mcp/backlog -f Dockerfile .

Extending the Server

To add new tools:

  1. Define a new Zod schema in src/core/schema.ts

  2. Add a new tool definition in src/tools/toolDefinitions.ts and include it in ALL_TOOLS

  3. Create a new handler in src/tools/handlers.ts and register it in toolHandlers

  4. Implement business logic in a service in the src/services/ directory

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

12 tools
backlog_add_issueC

Add an issue using the Backlog Issue API.

Inputs: issueTypeId (required), priorityId (required), projectId (required), summary (required), +9 more.

backlog_add_wikiC

Add an wiki using the Backlog Wiki API.

Inputs: content (required), name (required), projectId (required), mailNotify.

backlog_delete_issueC

Delete an issue using the Backlog Issue API.

Inputs: issueIdOrKey (required).

backlog_delete_wikiC

Delete an wiki using the Backlog Wiki API.

Inputs: wikiId (required), mailNotify.

backlog_get_issueC

Performs an issue get using the Backlog Issue API.

Inputs: issueIdOrKey (required).

backlog_get_issuesC

Performs list issue get using the Backlog Issues API. Supports pagination, content filtering. Maximum 20 results per request, with offset for pagination.

Inputs: assigneeId, count, createdSince, createdUntil, +7 more.

backlog_get_projectC

Performs an project get using the Backlog Project get API.

Inputs: projectIdOrKey (required).

backlog_get_projectsB

Performs list project get using the Backlog Projects get API. Supports pagination, content filtering. Maximum 20 results per request, with offset for pagination.

Inputs: all, archived.

backlog_get_wikiC

Performs an wiki get using the Backlog Wiki API.

Inputs: wikiId (required).

backlog_get_wikisC

Performs list wikis get using the Backlog Wiki API

Inputs: projectIdOrKey (required), keywords.

backlog_update_issueB

Update an issue using the Backlog Issue API.

Inputs: issueIdOrKey (required), actualHours, assigneeId, attachmentId, +14 more.

backlog_update_wikiC

Update an wiki using the Backlog Wiki API.

Inputs: wikiId (required), content, mailNotify, name.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools are organized by resource type (issue, wiki, project) and action (add, delete, get, update), making it easy for an agent to select the correct one. There's no overlap in functionality between tools.

    Naming Consistency5/5

    All tool names follow a perfect and consistent pattern: 'backlog_' prefix + verb (add, delete, get, update) + singular/plural noun (issue, wiki, project). The naming is systematic and predictable throughout the entire set.

    Tool Count5/5

    12 tools is well-scoped for a Backlog server covering issues, wikis, and projects. Each tool earns its place with clear CRUD operations for each resource type, providing comprehensive coverage without being overwhelming.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for all three resource types (issues, wikis, projects). There are no obvious gaps - each resource has add, delete, get (both single and list), and update operations where applicable.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      C
      quality
      D
      maintenance
      This is an MCP server that facilitates building tools for interacting with various APIs and workflows, supporting Python-based development with potential for customizable prompts and user configurations.
      1
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that provides tools for interacting with Linear issue tracking system, currently supporting issue search with plans to expand to issue creation, updates, comments, and project management.
      2,467 npm
      1
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Linear project management systems, allowing users to retrieve, create, and update issues, projects, and teams through natural language.
      198
      85,521 npm
      149
      MIT