pulsemcp verified Safe content atomic mcp-remote

Emacs Lisp Development

This MCP server provides Emacs Lisp development assistance through five specialized tools that enable AI agents to interact with Emacs environments for code analysis and documentation lookup. Built by Laurynas Biveinis using TypeScript with the mcp-server-lib foundation, it offers function documentation retrieval, source code definition extraction with header comments, variable information without exposing values, Info documentation lookup from the Emacs Lisp Reference Manual, and secure source file reading from system directories and ELPA packages. The implementation features robust security controls that prevent path traversal attacks, handles both regular and byte-compiled functions, supports dynamic and lexical binding contexts, manages function aliases and C-implemented functions, and provides complete source reconstruction for interactively defined functions, making it valuable for AI-assisted Emacs Lisp development, code exploration and analysis, package development workflows, and building AI tools that need deep integration with Emacs internals.

Cognium trust score

100%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: ai-ml
Source: PulseMCP
Repository: github.com/laurynas-biveinis/elisp-dev-mcp
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Emacs Lisp Development from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"