Skip to main content
Glama
rsascha

mcp-debug-claude-desktop

by rsascha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-debug-claude-desktop

No user-submitted related servers found.

    Related Servers

    • my-mcp-server

      15972289829
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.
      25 npm
      -

    • MCP Server

      johnleider
      A
      license
      Not graded
      quality
      D
      maintenance
      A Machine Context Protocol server that enables Claude AI to interact with tools through a structured communication interface, following standard MCP patterns with server initialization and stdio transport.
      681 npm
      2
      MIT

    • routine-mcp

      rskmanz
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server built with the mcp-framework for developing and managing custom tools. It provides a structured foundation for building and integrating modular components like data processors and API clients into Claude Desktop.
      5 npm
      -

    • Example MCP Server

      VIGNESH-2232005
      A
      license
      Not graded
      quality
      D
      maintenance
      A Node.js/TypeScript MCP server template with sample tools (ping and system_info) that demonstrates how to build custom tools for Claude Desktop using stdio transport.
      4 npm
      ISC

    • debug-mcp-server

      silentwasd
      F
      license
      Not graded
      quality
      C
      maintenance
      A minimal MCP server for debugging MCP clients. It echoes back everything it receives — tool arguments, session IDs, metadata — so you can inspect exactly what your client is sending.
      -
    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 4 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: ping for round-trip verification, echo for text return, sized_echo for size effects, and slow_echo for delay effects. There is no ambiguity between them.

    Naming Consistency4/5

    Names are clear and follow a consistent style: all lowercase with underscores. The echo variants (sized_echo, slow_echo) follow a clear adjective_echo pattern, though ping and echo are simpler bare verb forms.

    Tool Count5/5

    Four tools is an ideal size for a debug server, covering essential test scenarios without bloat. Each tool earns its place.

    Completeness4/5

    The set covers basic connectivity, text echo, size testing, and latency testing. A potential gap is error injection or message corruption testing, but for the stated debug purpose, coverage is solid.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources