backlog

This MCP server provides an interface to Backlog's API for searching, retrieving, and updating issues. It exposes a client built on top of a Node.js entry point (build/index.js) that communicates with your Backlog space using the configured credentials. To use it, configure the MCP settings in your environment so that the host application can start the backlog MCP server as a service. Once running, you can perform searches for issues, fetch specific issue details, and apply updates or comments to issues via the MCP server's API surface as described in your integration tool or editor (e.g., RooCline/Code mods). The server is designed to be used within a larger ecosystem of MCP-enabled clients, enabling consistent access to Backlog data across different applications.

Prerequisites:

• Node.js installed (recommended LTS version)
• Access to the backlog instance (space URL and API key)
• Optional: Docker if you prefer containerized setup

Option A: Run directly with Node.js

1. Clone the repository containing the backlog MCP server to your machine.
2. Install dependencies:
   • npm install
3. Create and configure environment variables or a settings file as required by your setup (see additional_notes for details).
4. Start the server by running:
   • node build/index.js

Option B: Run with Docker

1. Create a .env file with required environment variables, for example: BACKLOG_SPACE_URL=https://your-space.backlog.com BACKLOG_API_KEY=your_api_key
2. Build and start the container (docker-compose or docker run depending on your setup):
   • docker compose up -d --build
3. Ensure the container exposes/points to the same settings the MCP expects (see the backlog mcp_settings.json example in the docs).

Environment variables commonly used:

• BACKLOG_SPACE_URL: The base URL of your Backlog space (e.g., https://your-space.backlog.com)
• BACKLOG_API_KEY: API key with appropriate permissions

Configuration tips:

• The MCP server is configured via the backlog entry in your cline_mcp_settings.json (or equivalent) with command: node and args: ["build/index.js"], and a working directory (cwd) pointing to your backlog-mcp-server project path.
• If deploying with Docker, you can wrap the same settings inside the docker exec approach shown in the readme, using env to pass BACKLOG_SPACE_URL and BACKLOG_API_KEY.
• Ensure network access between the MCP host and the Backlog API, and that the API key has permission to search, retrieve, and update issues.

Common issues:

• Misconfigured cwd or incorrect path to build/index.js will prevent the server from starting.
• Missing environment variables can cause authentication failures; verify the BACKLOG_SPACE_URL and BACKLOG_API_KEY are correctly provided.
• When using Docker, make sure the environment variables are accessible to the container and that the container has network access to Backlog.