backlog

This MCP server provides a Backlog API surface that lets you manage projects, issues, users, files, and comments through a set of tool endpoints. Core capabilities include retrieving a list of spaces and projects, listing and filtering issues, viewing and updating individual issues, creating new issues, adding comments, and performing search queries across issues and projects. It is designed to be used both programmatically and via CLIs or integrations (for example in Claude Desktop) by wiring the appropriate Backlog domain and API key as environment variables. The included tools map to common Backlog operations such as getting all projects (getProjects), fetching issues (getIssues) for a project, creating or updating issues (createIssue, updateIssue), and adding comments (addComment). For local runs, you can supply BACKLOG_DOMAIN and BACKLOG_API_KEY to authorize requests; optional testing helpers can be provided via TEST_PROJECT_ID or TEST_PROJECT_KEY for safe test runs.

Prerequisites:

• Node.js and npm installed on your system
• Access to a Backlog instance and an API key

Installation steps:

1. Clone the MCP server repository or install via npm/pnpm if published
2. Install dependencies npm install
3. Configure environment variables (see below) or create a .env file with: BACKLOG_DOMAIN=your-domain.backlog.com BACKLOG_API_KEY=your-api-key TEST_PROJECT_ID=your-test-project-id (optional) TEST_PROJECT_KEY=your-test-project-key (optional)
4. Build the project (if required by the repo): npm run build
5. Run the server: npm start

Usage note:

• If you prefer using NPX (for example in Claude Desktop), you can run the MCP server directly with: npx -y @tmhr1850/backlog-mcp-server and supply environment variables as needed.

Tips and considerations:

• Required env vars: BACKLOG_DOMAIN and BACKLOG_API_KEY. These authorize requests to your Backlog instance.
• Optional test vars: TEST_PROJECT_ID and TEST_PROJECT_KEY can help with test runs without affecting production data.
• The MCP exposes several operations: getSpaces, getProjects, getIssues, getIssue, createIssue, updateIssue, addComment, and searchIssues. Use appropriate arguments as documented in the README to construct requests.
• When using NPX, the package will be fetched at runtime; ensure network access and npm permissions are available.
• Results for list-type calls may be paginated (e.g., max 100 items for getIssues). Use offset to page through results.
• If you deploy in Claude Desktop or similar, you can embed the server config into claude_desktop_config.json under mcpServers with the necessary env values.