Skip to main content
Glama
Sign In
backlog-mcp

backlog-mcp

by danglephuc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to backlog-mcp

No user-submitted related servers found.

    Related Servers

    • aiboard

      flashist
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to manage a filesystem-based issue tracker through typed MCP tools such as list_tasks, create_task, change_task_status, log_work, and get_sprint, instead of shelling out to a CLI. Tasks and sprints are plain folders of Markdown files, so agents can create, claim, comment on, and move work by topic without any database or server state.
      20
      MIT

    • gadak

      midagedev
      A
      license
      Not graded
      quality
      A
      maintenance
      Keeps Jira Cloud, Jira Server, Linear or its own built-in tracker (plus Confluence pages) in one local SQLite file. Its MCP tools answer from that file: read-only SQL, full-text search across issues, comments and wiki pages, issue detail, sprint and retro reads.
      47
      Apache 2.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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
    ResponsivenessOutdated data

    Resources