Mcp Backlog

io.github.vfa-khuongdvPublished by GitHub account vfa-khuongdvv1.0.0Updated Oct 24, 2026

MCP server for Backlog API integration with AI agents.

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

Local MCP server that connects an AI assistant to a Backlog instance's API, using a Backlog API key and host URL.

What you can do
  • Connects an assistant to the Backlog project-management API.
  • No tools are listed in the manifest, so the exact operations are not documented here; expect project, issue and related Backlog data access through the API.
  • Runs as a local stdio process started on the user's machine.
When to use it
Worth adding if your team tracks projects and issues in Backlog and you want an assistant to work with that data directly instead of copying it by hand.
Requirements
Runs locally over stdio from the npm package @duongkhuong/mcp-backlog, so Node.js is needed. Requires two environment variables: BACKLOG_HOST with your Backlog instance URL and BACKLOG_API_KEY with an API key from your account settings. Desktop only; no web execution.
Before you install
The server needs a Backlog API key (BACKLOG_API_KEY), which grants access to your Backlog account data; store it in the environment rather than in shared configs. The manifest lists no tools, so what it can read or change in your Backlog space is not documented here; review the package before use.

Installation

In SourceWeft

  1. Open Mcp Backlog in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.