Issues, pull requests, wikis and documents all get read and write tools, so an agent can move a ticket forward instead of only reporting on it. If you would rather it could not, the write tools are compile-time features you can omit, and the key it runs under can be limited to the projects you name.
A Rust server for Backlog that puts one space's issues, Git repositories, wiki pages, documents, shared files and project reference data behind tools. Tool names follow a category-resource-action pattern, so a client that filters by name prefix can allow one family at a time.
- Issue work end to end — read one, list the issues in a milestone, update fields including custom ones, add and edit comments
- New issues filed into a project, custom field values included
- Pull request review material: repositories, PR details, comments and attachments, plus posting a comment back
- Wiki pages listed, read and updated, with their attachments
- The project's document tree, a single document in full, and adding or deleting one
- The reference data an agent needs before it writes anything — statuses, issue types, custom field definitions, priorities, the users in the space
- Attachment downloads that come back as an image, as text, or as raw bytes, with an override when the detection guesses wrong
Your Backlog space address and an API key you issue from your own Backlog settings, both handed over by the client that launches the server. It installs from the author's Homebrew tap on macOS and Linux, from prebuilt binaries elsewhere, or you build it with the Rust toolchain. Access can be pinned to a named set of project keys, and the write tools are build-time features you can leave out.
One command plus a key — brew install mcp-backlog-server, then supply credentials