Skip to main content
Glama
kongyo2

MCP Dev MCP

by kongyo2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCP Dev MCP

No user-submitted related servers found.

    Related Servers

    • MCP Inspector as MCP Server

      esinecan
      A
      license
      A
      quality
      B
      maintenance
      Enables LLMs to inspect and test other MCP servers by listing and calling their tools, reading resources, and getting prompts. Supports stdio, SSE, and HTTP transports for both local and remote MCP server inspection.
      7
      4 npm
      1
      MIT

    • MCP Inspector Assistant

      mcpassistant
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides programmatic access to MCP server testing, debugging, and validation capabilities by wrapping the official MCP Inspector. Enables users to test tools, validate protocol compliance, discover server capabilities, and debug MCP servers through natural language interactions.
      -

    • McpHub

      John0King
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.
      2
      MIT

    • MCP Workbench MCP Server

      raeseoklee
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to programmatically inspect, test, and validate other MCP servers by exposing MCP Workbench capabilities as structured tools. It supports automated test spec generation, execution, and detailed failure analysis to ensure server reliability.
      4
      5 npm
      Apache 2.0
    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.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: call_tool executes tools, get_prompt retrieves prompts, list_prompts lists prompts, list_resources lists resources, list_tools lists tools, and read_resource reads resources. The descriptions clearly differentiate their functions, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern with the prefix 'mcpdev_inspector_' followed by a verb_noun structure (e.g., call_tool, get_prompt, list_prompts). This predictability makes the tool set easy to navigate and understand.

    Tool Count5/5

    With 6 tools, this server is well-scoped for its purpose of inspecting and interacting with MCP servers. Each tool serves a specific role in discovery and execution, with no redundancy, making the count appropriate and efficient.

    Completeness5/5

    The tool set provides complete coverage for the MCP server inspection domain, including listing tools, prompts, and resources, reading resources, getting prompts, and calling tools. There are no obvious gaps, enabling agents to perform all essential inspection and interaction tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources