Skip to main content
Glama
fleagne

Backlog MCP Server

by fleagne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Backlog MCP Server

No user-submitted related servers found.

    Related Servers

    • Linear

      tacticlaunch
      A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Linear project management systems, allowing users to retrieve, create, and update issues, projects, and teams through natural language.
      198
      30,748 npm
      147
      MIT

    • MCP Server Linear

      floodfx
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that provides tools for interacting with Linear issue tracking system, currently supporting issue search with plans to expand to issue creation, updates, comments, and project management.
      2,176 npm
      1
      MIT

    • Backlog MCP Server

      TanLeJS
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that enables AI agents to interact with Backlog API for managing projects, issues, wikis, Git repositories, and other Backlog features.
      -

    • Lodestar MCP Server

      kanlanc
      F
      license
      C
      quality
      D
      maintenance
      This is an MCP server that facilitates building tools for interacting with various APIs and workflows, supporting Python-based development with potential for customizable prompts and user configurations.
      1
      -
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools are organized by resource type (issue, wiki, project) and action (add, delete, get, update), making it easy for an agent to select the correct one. There's no overlap in functionality between tools.

    Naming Consistency5/5

    All tool names follow a perfect and consistent pattern: 'backlog_' prefix + verb (add, delete, get, update) + singular/plural noun (issue, wiki, project). The naming is systematic and predictable throughout the entire set.

    Tool Count5/5

    12 tools is well-scoped for a Backlog server covering issues, wikis, and projects. Each tool earns its place with clear CRUD operations for each resource type, providing comprehensive coverage without being overwhelming.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for all three resource types (issues, wikis, projects). There are no obvious gaps - each resource has add, delete, get (both single and list), and update operations where applicable.

    Resources