Backlog MCP

Connect your AI tools to Nulab Backlog using the Model Context Protocol (MCP) through Cequence AI Gateway. The Backlog MCP server gives AI assistants secure access to your Backlog space for managing projects, issues, comments, wikis, version milestones, Git repositories, pull requests, documents, and notifications.

Overview

Backlog MCP is the official nulab/backlog-mcp-server. Unlike vendor-hosted remote MCP servers, you host this server yourself (via Docker or npx) and run it with the Streamable HTTP transport. You then connect Cequence AI Gateway to the public URL of your deployment.

• Server URL: https://<your-mcp-host>/mcp (your own deployment)
• Transport: HTTP (Streamable HTTP)
• Hosted by: You (self-hosted)
• Backlog space: Your *.backlog.com, *.backlog.jp, or *.backlogtool.com space

Backlog is a project and code management platform from Nulab used by teams for issue tracking, version control (Git), wikis, and documents. The MCP server exposes 58 tools spanning space administration, projects, issues, wikis, Git/pull requests, documents, and notifications.

Self-hosted deployment required

There is no vendor-hosted Backlog MCP endpoint. You must deploy the server yourself behind TLS before connecting it to the gateway. The default bind is 127.0.0.1:3333 with path /mcp; expose it over the network only with authentication and TLS enabled, because the tools provide full access to your Backlog API.

Supported authentication types

Type	Supported	Notes
OAuth 2.0	Yes	Recommended for Cequence AI Gateway. Run the server in OAuth mode so each user authenticates with their own Backlog account. Supports Dynamic Client Registration (DCR) and standard discovery endpoints.
API key	Yes	The server can run with a single shared Backlog API key (BACKLOG_API_KEY) instead of OAuth. All actions then use that key's permissions.

When run in OAuth mode, the Backlog MCP server acts as both an OAuth authorization server (for MCP clients such as the gateway) and an OAuth client (for Backlog). It exposes:

• GET /.well-known/oauth-authorization-server
• GET /.well-known/oauth-protected-resource/mcp
• POST /register (Dynamic Client Registration)
• GET /authorize, GET /callback, POST /token

This lets Cequence AI Gateway complete the OAuth flow automatically.

What can you do with this MCP server

The Backlog MCP server groups its tools into toolsets. Capabilities are grouped by area below.

Space and users

• Get information about the Backlog space
• List space activities and a specific user's recent updates
• List users in the space and get the authenticated user (get_myself)
• Get the count of stars received by a user

Projects

• List, create, get, update, and delete projects

Issues

• Get a single issue, list issues with rich filtering, and count issues
• Create, update, and delete issues (including custom fields)
• Get and add issue comments
• List priorities, categories, custom fields, issue types, and resolutions
• Manage watching lists: list items, get counts, add, update, delete, and mark watches as read
• Manage version milestones: list, add, update, and delete versions

Wiki

• List wiki pages, count wikis, and get a specific wiki page
• Create and update wiki pages

Git and pull requests

• List Git repositories and get a specific repository
• List and count pull requests, and get a specific pull request
• Create and update pull requests
• List, add, and update pull request comments

Documents

• List documents in a project, get the document tree, and get a specific document
• Add a new document

Notifications

• List notifications and count notifications
• Reset the unread notification count and mark a notification as read

Multi-organization

• list_organizations returns the configured Backlog organizations and identifies the default (when the server is configured for multiple Backlog organizations). Most tools accept an optional organization parameter to route the request.

Prerequisites

Before adding Backlog MCP in Cequence AI Gateway, ensure you have:

• Access to Cequence AI Gateway at aigateway.cequence.ai
• A Nulab Backlog account and space with API access enabled
• A deployed Backlog MCP server reachable over HTTPS, running with MCP_TRANSPORT=http (Streamable HTTP)
• For OAuth authentication: an OAuth application registered in your Backlog space (Personal Settings → Register Application) with the redirect URI set to <MCP_SERVER_BASE_URL>/callback, plus the environment variables BACKLOG_OAUTH_CLIENT_ID, BACKLOG_OAUTH_CLIENT_SECRET, and MCP_SERVER_BASE_URL set on the server
• For API key authentication: a Backlog API key set as BACKLOG_API_KEY (and BACKLOG_DOMAIN) on the server

Example: running the server in OAuth mode

BACKLOG_DOMAIN=your-space.backlog.com \
BACKLOG_OAUTH_CLIENT_ID=your-client-id \
BACKLOG_OAUTH_CLIENT_SECRET=your-client-secret \
MCP_SERVER_BASE_URL=https://your-mcp-host \
node build/index.js --transport http --http-host 0.0.0.0 --http-port 3333 --http-path /mcp

Example workflows

Once connected, you can run workflows like these from your AI client.

Project and issue tracking

• "List all my Backlog projects."
• "Create a new bug issue in the PROJECT-KEY project with high priority titled 'Fix login page error'."
• "Show me all overdue issues assigned to me."
• "Add a comment to PROJECT-123 letting the assignee know it's ready for review."

Git and pull requests

• "List all Git repositories in the PROJECT-KEY project."
• "Show me all open pull requests in the repository 'repo-name' of PROJECT-KEY."
• "Create a pull request from 'feature/new-feature' to 'main' in 'repo-name'."

Wikis and documents

• "Find wiki pages about onboarding in PROJECT-KEY."
• "Create a wiki page with this week's release notes."
• "Show me the document tree for the PROJECT-KEY project."

Notifications and watching

• "How many unread notifications do I have?"
• "Show me everything I'm watching."

Connecting MCP server from Cequence AI Gateway

1. Log in to Cequence AI Gateway.
2. Choose your tenant.
3. Go to App catalogue.
4. Filter by Remote MCP server.
5. Search for Backlog MCP and then select it.
6. Select Create MCP server.
7. Enter the URL of your deployed Backlog MCP server (for example, https://your-mcp-host/mcp).
8. Choose the auth method (OAuth 2.0 or API key) matching how you deployed the server, and complete the setup as prompted.
9. Select tools and deploy.

Use the generated MCP server URL in your client (Claude, Cursor, Windsurf, etc.) as described in the Client Configuration docs. For detailed UI steps and screenshots, see Create a third-party MCP Server.

Additional information specific to Backlog MCP

• Self-hosting: You are responsible for deploying, securing (TLS), and maintaining the Backlog MCP server. See the project README for Docker and npx instructions.
• Toolsets: The server can selectively enable toolsets (space, project, issue, wiki, git, notifications, document) via --enable-toolsets or ENABLE_TOOLSETS. The project toolset is recommended as many tools rely on project data.
• OAuth limitations: OAuth mode currently supports a single Backlog organization, and client registrations and tokens are stored in memory (lost on server restart).
• Permissions: In OAuth mode, all actions respect the authenticated user's Backlog permissions. In API key mode, all actions use the permissions of the configured key.
• Official documentation: For setup, transport, and authentication details, see the Backlog MCP Server on GitHub.