Skip to main content
Glama
flesler

MCP Tools

by flesler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCP Tools

No user-submitted related servers found.

    Related Servers

    • Locus

      paladini
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that gives AI coding agents codebase navigation intelligence, enabling symbol lookup, reference finding, type inspection, and diagnostics through tools like locate, refs, hover, diagnostics, status, and rename.
      569 npm
      MIT

    • better-mcp

      erquier
      A
      license
      A
      quality
      B
      maintenance
      A universal MCP server that provides AI agents with structured tools for filesystem, database, shell, and git operations, enabling seamless interaction with projects.
      19
      MIT

    • reference-mcp

      mark-burg
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that helps AI agents comprehend a codebase by providing tools for navigating, searching, and understanding code structure and history.
      10
      MIT

    • codeweave-mcp

      semihkayan
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI agents structured code understanding and precise code intelligence via local indexing of AST, call graphs, and semantic search.
      47 npm
      4
      Apache 2.0

    • MCP Codebase Server

      DmitriyOT
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for semantic codebase navigation that builds an AST index of symbols, imports, and exports, providing AI agents with tools to search, explore, and understand code.
      MIT
    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

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: insert_text for line-based file editing, os_notification for system alerts, and read_symbol for symbol extraction. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with a verb_noun structure (insert_text, os_notification, read_symbol). This uniformity enhances readability and predictability across the tool set.

    Tool Count3/5

    With only 3 tools, the set feels thin for a general-purpose 'MCP Tools' server, potentially lacking coverage for common operations like file reading or deletion. However, the tools are well-defined, so it's borderline but not severely mismatched.

    Completeness2/5

    The tool set has significant gaps for a file and system operations domain: there is no tool for reading file contents (only symbol extraction), deleting files, or basic file management. This incompleteness will likely cause agent failures in broader workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources