ragmacs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EMACS_SOCKET_NAME | No | The socket name or path for the Emacs server. Useful if multiple Emacs servers are running and you need to target a specific one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| elisp_evalC | Evaluate an arbitrary Elisp expression and return the result. |
| symbol_existsB | Check if a symbol exists in obarray. Returns symbol name or nil. |
| load_pathsB | Return the user's Emacs load paths. |
| list_featuresA | Return the list of currently loaded Emacs features. |
| list_manualsB | Return a list of available Info manual names. |
| list_manual_nodesB | Return all node names within a given manual. |
| manual_node_contentsB | Return the full text of a node in an Info manual. |
| check_featureB | Check whether a specific feature is loaded or available. |
| library_sourceB | Return the full source code of an Elisp library. |
| symbol_manual_sectionC | Return the manual section that documents a given symbol. |
| function_sourceB | Return the source code of a function or macro. |
| variable_sourceC | Return the source code of a defvar or defcustom. |
| variable_valueC | Return the current global value of a variable. |
| function_documentationB | Return the docstring for a function or macro. |
| variable_documentationC | Return the docstring for a defvar or defcustom. |
| function_completionsC | Return all function names matching a prefix using orderless. |
| command_completionsB | Return all interactive commands matching a prefix. |
| variable_completionsC | Return all variables matching a prefix using orderless. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
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.
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.
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.
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.