Skip to main content
Glama
danglephuc

backlog-mcp

by danglephuc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to backlog-mcp

No user-submitted related servers found.

    Related Servers

    • Anamnesis

      oscardvs
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a local-first, file-based memory layer for Claude Code that syncs across machines via git over private networks, with MCP tools for search, write, and sync of human-readable markdown notes.
      Apache 2.0

    • bgl-mcp-server

      yuka-sakamaki777
      F
      license
      A
      quality
      D
      maintenance
      Enables users to interact with Backlog issues directly from VSCode/GitHub Copilot or Claude Desktop, providing tools to retrieve issues, list comments, and add comments.
      3
      -

    • backlog-mcp

      corbym
      A
      license
      A
      quality
      B
      maintenance
      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
      16
      3
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct role: syncing remote-to-local, local-to-remote, fetching a single issue, creating issues in bulk, listing local files, and testing connectivity. Sync-issues and update-issues are closely related as inverse operations, but their descriptions clarify direction. No two tools appear to do the same thing.

    Naming Consistency4/5

    Tool names mostly follow a verb-noun pattern: sync-issues, get-issue, update-issues, list-task-files, test-connection. Minor inconsistency exists with get-issue singular versus plural elsewhere, and bulk-create-tasks uses a compound verb prefix. Overall the pattern is predictable and readable.

    Tool Count5/5

    Six tools is well-scoped for a Backlog-to-local-file synchronization server. Each tool covers a necessary operation without redundancy or bloat. The count feels appropriate for the stated purpose.

    Completeness4/5

    The tool set covers the core sync workflow: test connection, read local files, fetch remote issues, push updates, and bulk-create issues from local files. A single-issue create or delete operation is missing, but the bulk-create and update tools cover the main lifecycle needs. Minor gaps exist but agents can likely complete typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources