Skip to main content
Glama
spranab

Project Tracker MCP Server

by spranab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Project Tracker MCP Server

No user-submitted related servers found.

    Related Servers

    • Trellis MCP

      langadventurellc
      A
      license
      Not graded
      quality
      D
      maintenance
      A file-backed MCP server for hierarchical project management that enables AI assistants to create, claim, and complete tasks within a project→epic→feature→task structure, with dependency management and Markdown-based storage.
      MIT

    • Saga MCP

      spranab
      A
      license
      B
      quality
      A
      maintenance
      A Jira-like project tracker MCP server for AI agents. SQLite-backed, per-project scoped, with full hierarchy and activity logging — so LLMs never lose track. No more scattered markdown files. saga-mcp gives your AI assistant a structured database to track projects, epics, tasks, subtasks, notes, and decisions across sessions.
      41
      1,538 npm
      35
      MIT

    • pg-mnemosyne-mcp

      Janadasroor
      A
      license
      B
      quality
      C
      maintenance
      🧠 A high-performance PostgreSQL-backed MCP server acting as a super memory, task tracker, and dynamic database manager for AI agents. Features built-in connection pooling, a professional tasks schema, and a unique shared multi-agent coordination hub to prevent coding conflicts in real-time.
      12
      3
      MIT

    • MCP Task Manager Server

      bsmi021
      A
      license
      A
      quality
      D
      maintenance
      A local Model Context Protocol server providing backend tools for AI agents to manage projects and tasks with persistent storage in SQLite, enabling structured tracking of project tasks with dependencies, priorities, and statuses.
      12
      9 npm
      25
      GPL 3.0

    • moo-tasks

      shekarsiri
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.
      9 npm
      2
      MIT
    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

    B3/5.0

    Scored across 40 tools

    Disambiguation4/5

    Each tool maps to a distinct entity and action (project, epic, story, issue, summary, status_update, context), so overlap is minimal. However, get_summary vs. get_project_summary and list_summaries vs. get_project_summary could cause some selection confusion.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (create_issue, list_projects, get_epic, delete_story, etc.). Compound entities like status_update are handled uniformly.

    Tool Count2/5

    40 tools is excessive for a project tracker, even with seven entity types. The full CRUD/listing/search surface for every entity creates bloat and increases the risk of agent misselection.

    Completeness5/5

    The tool set provides complete CRUD coverage for projects, epics, stories, issues, summaries, status updates, and context, plus search and summary operations. No obvious lifecycle operations appear to be missing.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources