Skip to main content
Glama
vivekhaldar

Emacs MCP Server

by vivekhaldar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Emacs MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Python Interpreter

      PortPro-Technologies-Inc
      F
      license
      A
      quality
      Not graded
      maintenance
      A Model Context Protocol server that allows LLMs to interact with Python environments, enabling code execution, file operations, package management, and development workflows.
      9
      -

    • Godot MCP

      bradypp
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to manage Godot projects, scenes, and editor operations through natural language commands.
      16
      238 npm
      90
      MIT

    • iTerm MCP Server

      rishabkoul
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with iTerm2 terminals, allowing creation and management of terminal sessions, command execution, and reading terminal output.
      5
      55 npm
      14
      ISC

    • Godot MCP

      Coding-Solo
      A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with the Godot game engine, allowing them to launch the editor, run projects, capture debug output, and control project execution.
      14
      238 npm
      5,787
      MIT

    • iTerm MCP

      lite
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that gives AI models access to your iTerm terminal session, allowing them to read output, write commands, and send control characters.
      3
      121 npm
      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

    C2.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one executes Emacs Lisp code, while the other generates it. There is no overlap or ambiguity between these functions, making it easy for an agent to select the appropriate tool based on the task.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with 'execute_emacs_lisp_code' and 'generate_emacs_lisp_code'. The naming is uniform, using snake_case and clear verbs that accurately describe each tool's action.

    Tool Count2/5

    With only two tools, the server feels thin for an Emacs integration, as it lacks operations like editing files, managing buffers, or handling common Emacs commands. This minimal set may limit agents in performing typical Emacs-related tasks.

    Completeness2/5

    The tool surface is severely incomplete for an Emacs server, covering only code execution and generation. It misses essential CRUD/lifecycle operations such as opening files, saving changes, or interacting with Emacs modes, which are core to the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources