Skip to main content
Glama
m-dev-tools

m-dev-tools-mcp

Official
by m-dev-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to m-dev-tools-mcp

No user-submitted related servers found.

    Related Servers

    • yala

      MalekYala
      A
      license
      A
      quality
      C
      maintenance
      MCP server exposing 570 config-driven dev tools across plan, develop, QA, feedback automation, and deploy stages, with meta-tools for searching and running them via natural language.
      4
      MIT

    • Repo Docs MCP

      pepperfm
      A
      license
      Not graded
      quality
      D
      maintenance
      A generic MCP server that exposes local repository checkouts, allowing users to search and read code and documentation through natural language. It supports multiple instances, enabling seamless interaction with various codebases via configurable tool prefixes and URI schemes.
      1,026 npm
      MIT

    • vera_mcp_service

      BKSLab
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP Tools Server that bridges the Agent Service with data services, currently enabling knowledge base search via the kb_search tool.
      -
    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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: describe returns pointers for typed IDs, route_intent maps natural language to IDs, and verify lists repo verification commands. No overlap is evident.

    Naming Consistency5/5

    All tool names are single imperative verbs or verb_noun pairs (route_intent). The naming pattern is consistent and predictable, with no mixed conventions.

    Tool Count4/5

    With only 3 tools, the set is on the lower end of the typical 3-15 range, but each tool serves a focused role within the catalog domain. Slightly thin but not insufficient.

    Completeness4/5

    The tools cover key query operations (describing, routing, verifying) for the catalog. Missing a tool to list all known kinds or types, but route_intent partially addresses this gap.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources