Skip to main content
Glama
SPECmd-app

specmd-mcp

Official
by SPECmd-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to specmd-mcp

No user-submitted related servers found.

    Related Servers

    • achmadya-dev/mcp-core

      achmadya-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a shared MCP SDK wrapper for building MCP servers with stdio transport, tool registration, JSON-safe responses, and environment helpers.
      42 npm
      MIT

    • ThinkRail

      andrewliu83
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables CLI coding agents to read, query, create, update, delete and validate a project's spec graph through seven spec_* tools, so specs act as the ground truth for every piece of work. The tools are exposed over an MCP stdio server that resolves the workspace root from the host session.
      Apache 2.0

    • deliverable-mcp

      Diski7
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to render Markdown to HTML, estimate page counts, verify document delivery constraints, and atomically ship documents through a zero-dependency JSON-RPC stdio server.
      4
      MIT

    • MCP-ToolHub

      vishwajitvm
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables secure discovery and invocation of sandboxed filesystem, repository inspection, and utility tools through a unified MCP client with schema validation, timeouts, and execution traces.
      -
    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

    C2.8/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct operations (create, inspect, blackbox, trace_create, trace_update, capabilities). However, 'validate_pair' is explicitly a narrower subset of 'validate', and 'inspect' vs 'blackbox' both produce reports, causing minor confusion. Descriptions clarify the boundaries, but two overlaps remain.

    Naming Consistency3/5

    The server mixes single verbs ('create', 'validate', 'inspect') with compound snake_case names ('trace_create', 'validate_pair') and nouns ('blackbox', 'capabilities'). While all lowercase and underscore-separated, the pattern is inconsistent. It is still readable but lacks a predictable verb_noun structure.

    Tool Count5/5

    Nine tools is well within the ideal 3–15 range for a spec and trace management server. Each tool appears to earn its place, aside from one nonfunctional tool. The count is appropriate and not bloated.

    Completeness3/5

    The surface covers creation, validation, inspection, and trace lifecycle, but lacks update/delete operations for the core SPEC.md file. Additionally, 'propose_patch' is not implemented, leaving a planned patch workflow incomplete. These are notable gaps for a complete spec management lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources