# Emacs MCP Server Model Context Protocol (MCP) server for Emacs. Enables generating and running elisp code in a running Emacs process. ## Tools The
Emacs MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. # Emacs MCP Server Model Context Protocol (MCP) server for Emacs. Enables generating and running elisp code in a running Emacs process. ## Tools The server exposes two tools: - generate_emacs_lisp_code: generates elisp for a given task -.
Once Emacs is connected, these are the calls the assistant has available:
generate_emacs_lisp_code — generates elisp for a given taskexecute_emacs_lisp_code — passes elisp to a running Emacs (via emacsclient) to eval and execute itYou will need 2 environment variables: OPENAI_API_KEY, EMACSCLIENT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Emacs's toolset — generate_emacs_lisp_code, execute_emacs_lisp_code — is a fair guide to whether it matches your workflow. It is maintained by vivekhaldar; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Emacs's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| generate_emacs_lisp_code | generates elisp for a given task |
| execute_emacs_lisp_code | passes elisp to a running Emacs (via emacsclient) to eval and execute it. |
| Variable | Description | Required |
|---|---|---|
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| EMACSCLIENT | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.