backlog-mcp
Rank #11411glama/corbym/backlog-mcp
An MCP server that gives AI agents structured read/write access to a story-based project backlog. Agents can list stories, read content, update status, and append notes — all backed by plain markdown files that live inside your project repository. There is no shared server. The backlog files live in your repo under requirements/, committed and versioned alongside your code
backlog-mcp is a Model Context Protocol (MCP) server published by corbym. It ranks #11411 of 58,832 servers tracked on MCP Toplist, and its repository has 2 GitHub stars. backlog-mcp is listed on Glama, and ships as a single rolling release with no explicit version metadata. It was first listed on Apr 13, 2026.
Ranks ahead of 47,421 of 58,832 servers on MCP Toplist.
Listed on 1 registry
corbym
Other servers by corbym
View all corbym servers →Not versioned
This server is published through a registry that does not expose explicit version metadata. The listing tracks a single rolling release.
Frequently asked questions
- What is backlog-mcp?
- An MCP server that gives AI agents structured read/write access to a story-based project backlog. Agents can list stories, read content, update status, and append notes — all backed by plain markdown files that live inside your project repository. There is no shared server. The backlog files live in your repo under requirements/, committed and versioned alongside your code
- Who maintains backlog-mcp?
- backlog-mcp is maintained by corbym, which publishes 2 MCP servers (0 total versions) tracked on MCP Toplist.
- Is backlog-mcp an official MCP server?
- backlog-mcp is not on the Official MCP Registry. It is listed on Glama.
- How many versions does backlog-mcp have?
- backlog-mcp ships as a single rolling release with no explicit version metadata.
- Where can I find the source code for backlog-mcp?
- The source code for backlog-mcp is hosted at github.com/corbym/backlog-mcp.