Backlog MCP Server

A Model Context Protocol (MCP) server for interacting with the Backlog API. This server provides tools for managing projects, issues, wiki pages, and

Remote serverstreamable-httpGo

What is the Backlog MCP server?

Backlog MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server for interacting with the Backlog API. This server provides tools for managing projects, issues, wiki pages, and more in Backlog through AI agents like Claude Desktop / Cline / Cursor etc.

What you get

  • Project tools (create, read, update, delete)
  • Issue tracking and comments (create, update, delete, list)
  • Version/Milestone management (create, read, update, delete)
  • Wiki page support
  • Git repository and pull request tools
  • Notification tools

What the assistant can call

Once Backlog is connected, these are the calls the assistant has available:

  • get_space — Returns information about the Backlog space
  • get_users — Returns list of users in the Backlog space
  • get_myself — Returns information about the authenticated user
  • get_project_list — Returns list of projects
  • add_project — Creates a new project
  • get_project — Returns information about a specific project
  • get_project_users — Returns list of users in a specific project
  • update_project — Updates an existing project
  • delete_project — Deletes a project
  • get_issue — Returns information about a specific issue
  • get_issues — Returns list of issues
  • count_issues — Returns count of issues

Configuration and credentials

You will need 8 environment variables: BACKLOG_DOMAIN, BACKLOG_API_KEY, TOOL_ADD_ISSUE_COMMENT_DESCRIPTION, TOOL_CREATE_PROJECT_DESCRIPTION, MAX_TOKENS, OPTIMIZE_RESPONSE, PREFIX, ENABLE_TOOLSETS. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Docker - A Backlog account with API access - API key from your Backlog account

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Backlog's toolset — get_space, get_users, get_myself and 11 more — is a fair guide to whether it matches your workflow. It is maintained by nulab; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Backlog.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the backlog mcp server does with a few real requests.

Available tools

ToolWhat it does
get_spaceReturns information about the Backlog space.
get_usersReturns list of users in the Backlog space.
get_myselfReturns information about the authenticated user.
get_project_listReturns list of projects.
add_projectCreates a new project.
get_projectReturns information about a specific project.
get_project_usersReturns list of users in a specific project.
update_projectUpdates an existing project.
delete_projectDeletes a project.
get_issueReturns information about a specific issue.
get_issuesReturns list of issues.
count_issuesReturns count of issues.
add_issueCreates a new issue in the specified project.
update_issueUpdates an existing issue.

How to install the Backlog MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Docker - A Backlog account with API access - API key from your Backlog account
VariableDescriptionRequired
BACKLOG_DOMAINConfiguration value read at startup.Optional
BACKLOG_API_KEYCredential the server authenticates with.Yes
TOOL_ADD_ISSUE_COMMENT_DESCRIPTIONConfiguration value read at startup.Optional
TOOL_CREATE_PROJECT_DESCRIPTIONConfiguration value read at startup.Optional
MAX_TOKENSCredential the server authenticates with.Yes
OPTIMIZE_RESPONSEConfiguration value read at startup.Optional
PREFIXConfiguration value read at startup.Optional
ENABLE_TOOLSETSConfiguration value read at startup.Optional

Example prompts to try

  • Use Backlog to get space.
  • Use Backlog to get users.
  • Use Backlog to get myself.

Frequently asked questions

It connects Backlog to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (get_space, get_users, get_myself, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Backlog directly.