Skip to main content
Glama
Sign In
Backlog MCP Server

Backlog MCP Server

by duytnb79
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

@duytnb79/backlog-mcp

A read-only MCP server for Backlog.

Quick start:

npx -y @duytnb79/backlog-mcp

Requirements

  • Node.js 20+

  • A Backlog API key

  • Your Backlog space URL

Related MCP server: Backlog MCP Server

Installation

Run directly with npx:

npx -y @duytnb79/backlog-mcp

Or install globally:

npm install -g @duytnb79/backlog-mcp
backlog-mcp

Configuration

Create a .env file or set environment variables before starting the server:

BACKLOG_BASE_URL="https://your-space.backlog.com"
BACKLOG_API_KEY="your_backlog_api_key"
BACKLOG_TIMEOUT_MS="10000"
BACKLOG_MAX_PAGE_SIZE="100"

The server automatically loads .env when running locally.

Required:

  • BACKLOG_BASE_URL

  • BACKLOG_API_KEY

Optional:

  • BACKLOG_TIMEOUT_MS

  • BACKLOG_MAX_PAGE_SIZE

Usage

With Claude Desktop

{
  "mcpServers": {
    "backlog-mcp": {
      "command": "npx",
      "args": ["-y", "@duytnb79/backlog-mcp"],
      "env": {
        "BACKLOG_BASE_URL": "https://your-space.backlog.com",
        "BACKLOG_API_KEY": "your_backlog_api_key"
      }
    }
  }
}

With a local clone

npm install
npm run build
cp .env.example .env
node dist/index.js

Available tools

  • get_notifications

  • read_notification

  • list_projects

  • list_repositories

  • list_pull_requests

  • get_pull_request

  • list_issues

  • get_issue

  • get_pull_request_comments

  • get_issue_comments

Security

  • Read-only access only

  • No hardcoded secrets

  • Requires an https Backlog base URL

  • No generic passthrough endpoint tool

Notes

  • Do not commit .env

  • Prefer one API key per teammate

  • Publishing this package does not expose Backlog data by itself; access still depends on each user's API key

Available Tools

10 tools
get_issueGet issueC

Get Backlog issue details.

Inputs: issueIdOrKey (required).

get_issue_commentsGet issue commentsC

Get comments for a Backlog issue.

Inputs: issueIdOrKey (required), minId, maxId, count, +1 more.

get_notificationsGet notificationsC

Get recent Backlog notifications.

Inputs: minId, maxId, count, order.

get_pull_requestGet pull requestC

Get Backlog pull request details.

Inputs: projectIdOrKey (required), repoIdOrName (required), pullRequestNumber (required).

get_pull_request_commentsGet pull request commentsC

Get comments for a Backlog pull request.

Inputs: projectIdOrKey (required), repoIdOrName (required), pullRequestNumber (required), minId, +3 more.

list_issuesList issuesC

List Backlog issues in accessible projects.

Inputs: projectId, projectKey, statusId, assigneeId, +6 more.

list_projectsList projectsC

List accessible Backlog projects.

Inputs: archived.

list_pull_requestsList pull requestsC

List pull requests in a Backlog git repository.

Inputs: projectIdOrKey (required), repoIdOrName (required), statusId, assigneeId, +3 more.

list_repositoriesList repositoriesC

List repositories in a Backlog project.

Inputs: projectIdOrKey (required).

read_notificationRead notificationC

Read full notification details.

Inputs: notificationId (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources and actions, such as get_issue vs. get_issue_comments or list_issues vs. list_pull_requests. There is no overlap or ambiguity that would cause misselection by an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, such as get_issue, list_projects, and read_notification. This predictability makes the set easy to navigate and understand.

    Tool Count5/5

    With 10 tools, the server is well-scoped for managing Backlog resources like issues, pull requests, projects, and notifications. Each tool earns its place without feeling excessive or insufficient for the domain.

    Completeness3/5

    The toolset covers read operations comprehensively but lacks create, update, or delete actions for issues, pull requests, or comments, which are common in project management workflows. This creates notable gaps that agents might struggle with for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • Backlog MCP Server

      fleagne
      A
      license
      B
      quality
      Not graded
      maintenance
      An MCP server implementation that integrates with Backlog API, enabling project management operations including issues, projects, and wikis through natural language interactions.
      12
      10,810 npm
      3
      -

    • Backlog MCP Server

      nulab
      A
      license
      C
      quality
      A
      maintenance
      A Model Context Protocol server that enables Claude to interact with Backlog project management tools through API integration, allowing management of projects, issues, wiki pages and other Backlog resources.
      64
      10,810 npm
      243
      MIT

    • jira-mcp-server

      chrisurf
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that provides AI agents structured access to Jira Cloud, enabling project listing, sprint overview, issue retrieval, and JQL search.
      1,650 npm
      MIT