Skip to main content
Glama
neatnettech

nod-mcp

Official
by neatnettech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nod-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-github-project-manager

      kunwarVivek
      A
      license
      C
      quality
      C
      maintenance
      Provides comprehensive tools for managing GitHub projects, milestones, tasks, and sprints. This server integrates deeply with GitHub Projects V2, offering features like automated kanban workflows, sprint planning, and custom field management.
      84
      95 npm
      104
      MIT

    • Project OS for Codex MCP

      gray451
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to read a project's Git-backed kickoff, acceptance criteria, handoff package, progress, and next step, and to append validated, audited progress events as project records. It provides short-lived scoped credentials and fail-closed tool allowlisting for safe, resumable AI-assisted development.
      -

    • MCP Project Manager

      HA2614
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides project management capabilities through terminal, web UI, or MCP stdio, including plans, code analysis, and filesystem-safe operations.
      7 npm
      MIT

    • projecttodo

      nidheesh1994
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to browse and manage local project to-do boards by listing, creating, updating, deleting, and organizing projects and tasks, including setting current work and adding drafts.
      3
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    D1.8/5.0

    Scored across 8 tools

    Disambiguation3/5

    Most tools have distinct resource+action names (e.g., work_item_list vs work_item_get), but 'board' is a bare noun with unclear scope and could overlap with work_item_list or timeline. The three view-like tools (board, timeline, dependency_graph) are conceptually separate but lack descriptions to clarify boundaries.

    Naming Consistency3/5

    Five tools follow a consistent resource_verb pattern (project_get, work_item_list, work_item_get, work_item_create, work_item_update), but 'board', 'timeline', and 'dependency_graph' break that pattern as bare nouns. The mix is readable but not uniform.

    Tool Count5/5

    Eight tools is a well-scoped number for a project management server, falling comfortably within the ideal 3–15 range. Each tool appears to cover a distinct operation or view without excessive redundancy.

    Completeness3/5

    The surface covers create, read (list/get), and update for work items, but lacks a delete operation and any create/list/update for projects (only project_get is present). Board and timeline tools are read-only, which may be acceptable but leaves lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources