Skip to main content
Glama
landermkerbey

ragmacs-mcp

by landermkerbey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ragmacs-mcp

No user-submitted related servers found.

    Related Servers

    • gerbil-mcp

      ober
      F
      license
      A
      quality
      C
      maintenance
      Provides AI assistants with live access to a Gerbil Scheme environment to evaluate expressions, look up module exports, and check syntax. It enables real-time interaction with the gxi runtime for macro expansion and symbol searching.
      6
      1
      -

    • Calva Backseat Driver

      BetterThanTomorrow
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Clojure REPLs for evaluating code, performing structural edits with bracket balancing, and looking up symbol documentation. Transforms AI coding assistants into interactive programming partners with access to runtime evaluation and real data structures.
      64
      MIT

    • 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
      9 npm
      1
      MIT

    • Epiverse MCP Server

      avinashladdha
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible LLM clients to access the Epiverse R package ecosystem, providing tools to list packages, retrieve package details and functions, search documentation and vignettes, and read source code directly from the local filesystem.
      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

    B3.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap in completion tools (function_completions, variable_completions, command_completions) and source/documentation tools (function_source vs library_source, function_documentation vs variable_documentation) that could cause mild confusion. However, the descriptions clarify the specific targets (functions vs variables vs commands), preventing major misselection.

    Naming Consistency5/5

    Tool names follow a highly consistent snake_case pattern with clear verb_noun structures (e.g., list_features, check_feature, elisp_eval). The naming is uniform across all tools, making it easy to predict and understand their functions without ambiguity.

    Tool Count4/5

    With 18 tools, the count is slightly high but reasonable for the domain of Emacs interaction and RAG, covering features, completions, documentation, source code, and manuals. It feels comprehensive without being overwhelming, though it borders on the heavier side for typical MCP servers.

    Completeness5/5

    The tool set provides complete coverage for interacting with Emacs: checking and listing features, evaluating code, retrieving completions, accessing documentation and source code for functions and variables, and navigating manuals. There are no obvious gaps; agents can perform a full range of queries and operations within this domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources