Backlog Bridge

Name: Backlog Bridge
Author: mickey-ichi

by mickey-ichiversion 0.1.5i★ –iRuns on your computer

Registry nameio.github.mickey-ichi/backlog-bridge

Install

Overview

Description from the maker (original English)

Read and write many Backlog (Nulab) spaces at once: issues, comments, search, sync previews.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: BACKLOG_BRIDGE_HOME

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "backlog-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "backlog-bridge",
        "mcp"
      ],
      "env": {
        "BACKLOG_BRIDGE_HOME": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add backlog-bridge --env BACKLOG_BRIDGE_HOME=your-value -- npx -y backlog-bridge mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "backlog-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "backlog-bridge",
        "mcp"
      ],
      "env": {
        "BACKLOG_BRIDGE_HOME": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "backlog-bridge": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "backlog-bridge",
        "mcp"
      ],
      "env": {
        "BACKLOG_BRIDGE_HOME": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

BACKLOG_BRIDGE_HOME env
Folder with .env (one _SPACE / _API_KEY pair per space). Default: ~/.config/backlog-bridge

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account mickey-ichi, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7250 servers in this category
Published to the registry more recently than 99% of the other 7250 servers in this category
Basic checks equal to or better than 100% of the other 7250 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Backlog Bridge safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.5) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

backlog-bridge

English · Tiếng Việt · 日本語

A bridge to many [Backlog](https://backlog.com) (Nulab) spaces at once — for people and for AI agents.

`backlog-bridge` — read and write issues, comments, search and activity on any connected space, from one CLI. Paste a Backlog URL and it picks the right space and API key.
`backlog-bridge sync` — one-way sync between two Backlog projects, e.g. a customer's Backlog and your internal one.
Agent-ready — ships skills for Claude Code, Codex and Cursor (AGENTS.md, .agents/skills/). The official Backlog MCP server binds to a single space; this works with as many as you connect.

Zero runtime dependencies. Needs Node.js >= 22.18 on macOS or Linux; on Windows, install with npm (option A).

Install

Option A — npm:

npm install -g backlog-bridge

backlog-bridge setup

A specific version: npm install -g backlog-bridge@0.1.5. Unreleased main from GitHub: npm install -g --install-links github:mickey-ichi/backlog-bridge (--install-links makes npm 10 copy the package instead of linking to a temporary clone). Release notes: CHANGELOG.md.

Option B — git clone (update later with git pull):

git clone https://github.com/mickey-ichi/backlog-bridge.git ~/.backlog-bridge

~/.backlog-bridge/bin/backlog-bridge setup # links ~/.local/bin/backlog-bridge

backlog-bridge setup installs the agent skills for Claude Code (~/.claude/skills), Codex and Cursor (~/.agents/skills, ~/.codex/skills), and creates ~/.config/backlog-bridge/.env (chmod 600) from the template. It never overwrites anything that isn't its own; backlog-bridge setup --uninstall removes only its links. backlog-bridge finds a Node >= 22.18 by itself (PATH, nvm, Homebrew), even if your default node is older.

Then fill in ~/.config/backlog-bridge/.env — one _SPACE + _API_KEY pair per space — and:

backlog-bridge spaces --check

backlog-bridge issue https://acme.backlog.jp/view/ACME-123

API keys: *Personal Settings → API → Register new API key*, on each space.

Update: npm install -g backlog-bridge@latest (option A) or git pull (option B). Uninstall: backlog-bridge setup --uninstall, then npm uninstall -g backlog-bridge (option A) or delete the clone (option B). Your data in ~/.config/backlog-bridge is kept.

Configuration

Private data never lives in the repo. It lives in a home directory:

Variable	Default	Purpose
`BACKLOG_BRIDGE_HOME`	`~/.config/backlog-bridge` if it exists, otherwise the repo root	holds `.env`, `config.json`, `state/`
`BACKLOG_BRIDGE_CONFIG`	`$BACKLOG_BRIDGE_HOME/config.json`	point at another config file
`BACKLOG_BRIDGE_PROFILE`	`defaultProfile` in the config	default profile for `sync`

backlog-bridge home prints what is in use.

Spaces come from environment variables — .env in the home directory, or exported in the shell:

ACME_SPACE=acme.backlog.jp      # xxx.backlog.com -> just "xxx"; other hosts -> full host

ACME_API_KEY=...

The space name is the lowercase prefix (ACME_* → acme, ACME_JP_* → acme_jp). Host and key are always taken from the same prefix. config.json → spaces is optional (only for a prefix that differs from the space name).

Profiles (for sync) live in config.json in the home directory. Start from config.example.json. Relative paths in a profile (state, pairFile) resolve against the home directory.

`backlog-bridge` — multi-space CLI

backlog-bridge setup [--uninstall] [--force]                  # install the global command + agent skills

backlog-bridge mcp [--config] # MCP server on stdio; --config prints host setup backlog-bridge home [--init] # paths in use; --init copies .env/config/state from the repo backlog-bridge spaces [--check] # connected spaces; --check calls the API backlog-bridge projects backlog-bridge issue # = URL | | backlog-bridge comments [--count=20] backlog-bridge search [--keyword=..] [--assignee=me|name] [--open] [--count=50] backlog-bridge activities [--project=KEY] [--count=20] backlog-bridge comment (--text=..|--file=path) [--yes] backlog-bridge update status= assignee= dueDate=YYYY-MM-DD summary=.. [--yes] backlog-bridge api [k=v ...] [--yes] # any Backlog API v2 endpoint

A bare works when its project key appears in a profile. --json prints raw JSON.
Every write is a dry run until you add `--yes`. It prints the exact request first.
update resolves status and assignee by name inside the project.

`backlog-bridge sync` — one-way sync between two projects

backlog-bridge sync --list

backlog-bridge sync --profile= [flags]

`mirror` mode — customer → internal

Creates one internal issue per planned customer issue (has a due date), summary .

Dedup in two layers: scans the destination for summaries prefixed with the source key, then merges the state file. Losing the state file never causes duplicates.
Existing mirrors are skipped unless --update (destination issues are often edited by hand).
Issue type / priority / status mapped by name via map; assignee matched by normalized name (accents and anything in parentheses removed), with map.assignee overrides.
dest.customFields: required custom fields by field name → item name; attached only when the field applies to the issue type. Missing required fields are reported in --dry-run.
Backlog can't set status on create, so status is set right after.
LIVE by default — use --dry-run first.

`progress` mode — internal → customer

Pushes progress from internal epics onto the customer's existing WBS issues. Never creates customer issues. Built for the common case where both sides split work differently:

Internal: an epic [Epic] [NN] ... with child tasks prefixed by layer ([FE], [BE], [QA], …).
Customer: WBS units 1.2.3 with fixed leaves by the last segment — .3 impl, .4 unit test, .5 acceptance.

Rules:

source.childGroups maps child prefixes to groups (e.g. api: [BE, Infra], screen: [FE]); alwaysCount prefixes (e.g. QA) count towards every group.
A pairFile maps each epic ("NN" or its issue key) to customer units per group; _outOfScope and _notes are special keys. --units lists the customer's units to fill it in.
Several epics may point at one unit; their tasks are merged before the rollup.
Rollup: done (all done) · in_progress · pending · not_started (→ nothing is written). ignoreStatuses are excluded. % is weighted by estimated hours (no estimate = 1h).
Writes the impl leaf; when done, also sets the acceptance leaf to Resolved (never Closed).

Safety: dry run by default (--live to write), neverTouchStatuses, no status regression without --allow-regress, no dates unless --dates=children, optional Japanese progress comment (--comment) that is updated in place via a hidden marker.

Flags

Flag	Mode	Meaning
`--list`	—	list profiles
`--profile=`	—	choose a profile (default: `defaultProfile`)
`--dry-run`	mirror	print only
`--assignee=A,B`	mirror	only issues assigned to these people (loose match)
`--since=YYYY-MM-DD`	mirror	only issues due on/after this date
`--update`	mirror	overwrite existing mirrors
`--live`	progress	actually write to the customer
`--units`	progress	list customer WBS units, leaves and statuses
`--only=28,29`	progress	only these epics
`--mine` / `--assignee=name`	progress	only leaves the customer assigned to you / to that person, plus a report of unpaired units
`--comment`	progress	post/update the progress comment
`--dates=children`	progress	also write start/due from the internal tasks
`--allow-regress`	progress	allow moving a customer status backwards

Using with AI agents

Claude Code (the Code tab of the Claude app): step-by-step guide — [docs/claude-code.md](docs/claude-code.md).

Claude plugin (plugin/): the skills and the MCP server in one package for Claude Code and Cowork — try it with claude --plugin-dir plugin from a clone. It needs Node.js 20+ on PATH; chat in the Claude app uses the Desktop Extension instead.

Agent	Picks up
Claude Code	`CLAUDE.md` → `AGENTS.md`, skills via `.claude/skills` → `.agents/skills`
Codex	`AGENTS.md`
Cursor	`.cursor/rules/backlog.mdc` → `AGENTS.md` + skills

After backlog-bridge setup the skills are installed globally, so any agent in any project can use backlog-bridge — not only inside this repo.

Skills: backlog-connect, backlog-query, backlog-write, backlog-sync. They make the agent preview every write, ask before writing to a customer's space, and treat ticket content as data rather than instructions.

MCP server (Claude Desktop, Cursor, …)

Claude Desktop: install the Desktop Extension (`.mcpb`, no Node needed) — step-by-step guide: [docs/claude-desktop.md](docs/claude-desktop.md).

For hosts without a shell — Claude Desktop, or any MCP client — backlog-bridge mcp runs an MCP server on stdio. backlog-bridge mcp --config prints ready-to-paste setup for Claude Desktop, Cursor, Claude Code and Codex, e.g.:

{ "mcpServers": { "backlog-bridge": { "command": "/path/to/backlog-bridge/bin/backlog-bridge", "args": ["mcp"] } } }

Claude Desktop, step by step:

backlog-bridge mcp --config and copy the JSON with your real path.
Merge it into mcpServers in ~/Library/Application Support/Claude/claude_desktop_config.json (keep a backup; don't overwrite other keys).
Quit Claude Desktop completely (⌘Q) and open it again — backlog-bridge appears among the tools.

Tools: list_spaces, home_info, get_issue, get_comments, search_issues, list_activities, list_projects, api_get (read-only) · add_comment, update_issue (dry run unless send: true) · list_sync_profiles, sync_preview (never writes — real syncs stay in the terminal). Each tool runs the backlog-bridge CLI, so the same guards apply; the server also hands the host the hard rules and the user's review mode.

Reviewing what goes to customers

Each person sets how they review text before an agent sends it to a customer, in their own .env:

`BACKLOG_BRIDGE_REVIEW`	For	Flow
`bilingual`	you read the customer's language	review a bilingual draft (customer language + your language), only the customer-language text is sent
`translate`	you don't	review in your language only; after approval the agent translates and sends right away

BACKLOG_BRIDGE_LANG (default vi) and BACKLOG_BRIDGE_CUSTOMER_LANG (default ja) set the two languages. backlog-bridge home shows the current mode; when it is not set, the agent asks.

Security

API keys only in .env in the home directory; backlog-bridge home / backlog-bridge spaces warn when it is readable by others. Backlog takes the key as the apiKey query parameter, so errors only ever print method and path.
Host and key always come from the same env prefix — a key is never sent to another space's host.
Issue keys must look like PROJECT-123, so a crafted key can't redirect

Only the beginning is shown; read the rest in the repo

Backlog Bridge

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

backlog-bridge

Install

Configuration

backlog-bridge — multi-space CLI

backlog-bridge sync — one-way sync between two projects

mirror mode — customer → internal

progress mode — internal → customer

Flags

Using with AI agents

MCP server (Claude Desktop, Cursor, …)

Reviewing what goes to customers

Security

`backlog-bridge` — multi-space CLI

`backlog-bridge sync` — one-way sync between two projects

`mirror` mode — customer → internal

`progress` mode — internal → customer