LABSCO SUMMARY

Full Backlog coverage, with the write half switchable off at build time.

Issues, pull requests, wikis and documents all get read and write tools, so an agent can move a ticket forward instead of only reporting on it. If you would rather it could not, the write tools are compile-time features you can omit, and the key it runs under can be limited to the projects you name.

What it is

A Rust server for Backlog that puts one space's issues, Git repositories, wiki pages, documents, shared files and project reference data behind tools. Tool names follow a category-resource-action pattern, so a client that filters by name prefix can allow one family at a time.

What you get

Issue work end to end — read one, list the issues in a milestone, update fields including custom ones, add and edit comments
New issues filed into a project, custom field values included
Pull request review material: repositories, PR details, comments and attachments, plus posting a comment back
Wiki pages listed, read and updated, with their attachments
The project's document tree, a single document in full, and adding or deleting one
The reference data an agent needs before it writes anything — statuses, issue types, custom field definitions, priorities, the users in the space
Attachment downloads that come back as an image, as text, or as raw bytes, with an override when the detection guesses wrong

Requirements

Your Backlog space address and an API key you issue from your own Backlog settings, both handed over by the client that launches the server. It installs from the author's Homebrew tap on macOS and Linux, from prebuilt binaries elsewhere, or you build it with the Rust toolchain. Access can be pinned to a named set of project keys, and the write tools are build-time features you can leave out.

Setup effort

One command plus a key — brew install mcp-backlog-server, then supply credentials

See installation options

USE CASES

01

Picking up an issue without opening Backlog

Read the issue and its comment thread, then edit the fields or reply in the same turn.

issue_details_getissue_comment_list_getissue_updateissue_comment_add

02

Seeing what is left in the current milestone

List the milestones on the project, pull the issues attached to the one you care about, and read them against the project's own status list.

issue_milestone_list_getissue_list_by_milestone_getproject_status_list_get

03

Reviewing a pull request in the conversation

Find the repository, open the pull request with its comment thread, and leave your review comment without switching windows.

git_repository_list_getgit_pr_list_getgit_pr_comment_list_getgit_pr_comment_add

04

Filing an issue that fills in the project's custom fields

Read the custom field definitions first, so the new issue arrives with the fields your team actually filters on already set.

project_custom_field_list_getissue_add

05

Keeping the wiki current after a change lands

Find the page, read what it says today, and write the updated text back.

wiki_list_getwiki_details_getwiki_update

36 tools

Listed in project docs. Your client may show a different list.

document_details_get

document_attachment_download

document_tree_get

document_add

document_delete

git_repository_list_get

git_repository_details_get

git_pr_list_get

git_pr_details_get

git_pr_attachment_list_get

git_pr_comment_list_get

git_pr_attachment_download

git_pr_comment_add

issue_details_get

issue_milestone_list_get

BEFORE YOU INSTALL

What to know first

Tools you get

36 tools named in the project's documentation. A read-only build with --no-default-features drops eight write tools, leaving 28. BACKLOG_PREFIX defaults to backlog_, so tools appear as backlog_issue_details_get rather than the documented issue_details_get.

Requires

BACKLOG_API_KEY in your environment

INSTALLATION

Connect your client

Server setup

Add the tap (only needed once):

TERMINAL

brew tap safx/tap
brew install mcp-backlog-server

Alternatively download a pre-built binary from the releases page, or clone the repository and run cargo build --release

Add the config block below to your MCP client config with your own BACKLOG_BASE_URL and BACKLOG_API_KEY

MCP Clients

Claude Desktop

CLAUDE DESKTOP · JSON

{
  "mcpServers": {
    "backlog": {
      "command": "<YOUR_PATH_TO_TARGET>/release/mcp-backlog-server",
      "args": [],
      "env": {
        "BACKLOG_BASE_URL": "https://<YOUR_SPACE>.backlog.com",
        "BACKLOG_API_KEY": "<YOUR_BACKLOG_API_KEY>",
        "BACKLOG_PROJECTS": "PROJ,DEMO",
        "BACKLOG_PREFIX": "backlog_"
      }
    }
  }
}

Cline

CLINE · JSON

{
  "mcpServers": {
    "backlog_mcp_server": {
      "autoApprove": [],
      "disabled": false,
      "timeout": 60,
      "command": "<YOUR_PATH_TO_TARGET>/release/mcp-backlog-server",
      "args": [],
      "env": {
        "BACKLOG_BASE_URL": "https://<YOUR_SPACE>.backlog.com",
        "BACKLOG_API_KEY": "<YOUR_BACKLOG_API_KEY>",
        "BACKLOG_PROJECTS": "PROJ,DEMO",
        "BACKLOG_PREFIX": "backlog_"
      },
      "transportType": "stdio"
    }
  }
}

Gemini CLI

GEMINI CLI · JSON

{
  "mcpServers": {
    "backlog_mcp_server": {
      "command": "<YOUR_PATH_TO_TARGET>/release/mcp-backlog-server",
      "timeout": 10000,
      "args": [],
      "env": {
        "BACKLOG_BASE_URL": "https://<YOUR_SPACE>.backlog.com",
        "BACKLOG_API_KEY": "<YOUR_BACKLOG_API_KEY>",
        "BACKLOG_PROJECTS": "PROJ,DEMO",
        "BACKLOG_PREFIX": "backlog_"
      }
    }
  }
}

Backlog Rust MCP Server