MCP.so
登录

Backlog MCP Server

@nulab

基本信息

分类

其他

许可证

MIT

传输方式

stdio

作者

nulab

关于 Backlog MCP Server

暂无概览

Backlog MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "backlog-mcp-server": {
      "command": "node",
      "args": [
        "build/index.js"
      ],
      "env": {
        "MCP_TRANSPORT": "http",
        "MCP_HTTP_PORT": "3333"
      }
    }
  }
}

Backlog MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Backlog MCP Server?

A Model Context Protocol (MCP) server for interacting with the Backlog API. It provides tools for managing projects, issues, wiki pages, and more through AI agents such as Claude Desktop, Cline, and Cursor.

How to use Backlog MCP Server?

Configure your MCP client (e.g., Claude Desktop) by adding the server definition with either Docker or npx, setting the environment variables BACKLOG_DOMAIN (your Backlog domain) and BACKLOG_API_KEY. The server runs by default via stdio; you can also enable HTTP transport (streamable HTTP) using --transport http. Optionally, you can enable OAuth 2.0 authentication for per-user access by setting BACKLOG_OAUTH_CLIENT_ID, BACKLOG_OAUTH_CLIENT_SECRET, and MCP_SERVER_BASE_URL.

Key features of Backlog MCP Server

  • Project tools (create, read, update, delete)
  • Issue tracking and comments (create, update, delete, list)
  • Version/milestone management (create, read, update, delete)
  • Wiki page support
  • Git repository and pull request tools
  • Notification tools
  • GraphQL-style field selection for optimized responses
  • Token limiting for large responses

Use cases of Backlog MCP Server

  • Manage Backlog projects and issues through a conversational AI assistant
  • Track and comment on issues without leaving the chat interface
  • Update wiki pages or browse Git pull requests via natural language commands
  • Automate bulk operations like creating versions or listing notifications
  • Integrate Backlog into multi-tool agent workflows (e.g., combining with search or code tools)

常见问题

1

What transports does the server support?

It supports **stdio** (default) and **HTTP transport** (Streamable HTTP). To use HTTP, start with `--transport http` or set `MCP_TRANSPORT=http`.

2

How do I enable OAuth authentication?

Set `BACKLOG_OAUTH_CLIENT_ID`, `BACKLOG_OAUTH_CLIENT_SECRET`, and `MCP_SERVER_BASE_URL` (public server URL). The server then exposes OAuth endpoints for MCP clients to authenticate each user independently.

3

Can I enable only some toolsets?

Yes, use the `--enable-toolsets` flag or `ENABLE_TOOLSETS` environment variable with a comma-separated list of toolset names (e.g., `space,project,issue`). By default, all toolsets are enabled.

4

What environment variables are required?

`BACKLOG_DOMAIN` and `BACKLOG_API_KEY` are required for API‑key auth. For HTTP transport, you can set `MCP_TRANSPORT`, `MCP_HTTP_HOST`, `MCP_HTTP_PORT`, and related variables.

5

What are the limitations of OAuth mode?

OAuth mode currently supports only a single Backlog organization; multi‑organization configuration is not compatible. Client registrations and tokens are stored in memory and lost on server restart.

评论

其他 分类下的更多 MCP 服务器