backlog-mcp-gateway
Interface with the Backlog platform's remote service endpoints for querying, fetching, and modifying item records, enabling seamless integration of task lifecycle operations into other applications.
Author

jootsuki
Quick Info
Actions
Tags
Backlog MCP Service Gateway
This is a Message Control Protocol (MCP) gateway specifically engineered to communicate with the Backlog service's external interface. It exposes core functionalities for issue lifecycle management.
Capabilities
- Issue record discovery (searching)
- Issue record retrieval (fetching details)
- Issue record modification (updating status, comments, etc.)
Deployment Configuration
Standard Client Setup
In your application's MCP configuration file, typically located at ~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json, incorporate the following server definition:
{ "mcpServers": { "backlog": { "command": "node", "args": ["build/index.js"], "cwd": "/path/to/backlog-mcp-server" } } }
Note: Ensure the value for cwd precisely matches the absolute path of the server's execution directory.
Containerized Operation (Docker)
Development Mode
For development and iterative testing utilizing containerization:
bash
Provision the environment variable template file
cp .env.example .env
Populate required credentials
BACKLOG_SPACE_URL=https://your-space.backlog.com BACKLOG_API_KEY=your_api_key
Build and initiate services in detached mode (with watching enabled)
NODE_ENV=development docker compose up -d --build
Development mode activates source file monitoring and automatic service restarts upon detected code changes.
Production Mode
For deployment in a production environment using Docker:
bash
Provision the environment variable template file
cp .env.example .env
Populate required credentials
BACKLOG_SPACE_URL=https://your-space.backlog.com BACKLOG_API_KEY=your_api_key
Build and initiate services in detached mode
docker compose up -d --build
Integration as an MCP Endpoint
To run the service inside a Docker container and expose it as an MCP endpoint to consuming applications (e.g., Cline, RooCline), update the client configuration file (cline_mcp_settings.json) as follows:
{ "mcpServers": { "backlog": { "command": "docker", "args": ["exec", "-i", "backlog-mcp-server", "node", "build/index.js"], "env": { "BACKLOG_SPACE_URL": "https://your-space.backlog.com", "BACKLOG_API_KEY": "your_api_key" } } } }
Further integration guides for other hosts:
Claude Desktop: https://ainow.jp/claude-mcp-guide/ Windsurf: https://zenn.dev/y16ra/articles/3ed3e2ae734fa4 Cursor: https://note.com/shuzon__/n/na2aafacf7324 →[Notion MCP Server Configuration for Cursor]
Example Interaction Prompts
md
Issue Search Commands
・Summarize all tickets under the 'PROJECT1' space associated with identifier '100' in Backlog. ・Report all issues currently in the 'In Progress' state within the 'PROJECT1' scope.
Issue Modification Commands
・Transition the status of ticket 'PROJECT1-100' to 'Completed'. ・Append the comment "This task is now finalized" to ticket 'PROJECT1-100'.
