elisp-dev-mcp
MCP ServerFree** - elisp (Emacs Lisp) development support tools, running in Emacs.
Capabilities11 decomposed
elisp-code-completion-with-context-awareness
Medium confidenceProvides intelligent code completion for Emacs Lisp by analyzing the current buffer context, function signatures, and variable bindings. Works by parsing the elisp AST to understand scope and available symbols, then filtering completion candidates based on semantic relevance rather than simple prefix matching. Integrates with Emacs' native completion UI to deliver suggestions inline.
Runs completion logic inside Emacs via MCP rather than as a separate language server, allowing direct access to Emacs' runtime symbol table and buffer state without serialization overhead
Faster and more accurate than regex-based completion because it leverages Emacs' native symbol introspection and live function definitions rather than static analysis
elisp-function-signature-extraction-and-documentation
Medium confidenceExtracts function signatures, argument lists, and docstrings from elisp code by introspecting function objects at runtime or parsing function definitions statically. Returns structured metadata including parameter names, optional/rest arguments, and documentation, enabling IDE-like hover hints and signature help. Integrates with MCP to deliver this metadata to client tools.
Combines runtime introspection (via Emacs' function-documentation and help-function-arglist) with static AST parsing to handle both loaded and unloaded code, providing complete signature coverage
More complete than static-only analysis because it accesses live function objects with their actual arity and docstrings, and more reliable than pure runtime introspection because it falls back to parsing for unloaded code
elisp-buffer-and-file-operations-via-mcp
Medium confidenceProvides MCP-based access to Emacs buffer and file operations, allowing external tools to read, write, and manipulate buffers and files within the Emacs session. Supports operations like opening files, creating buffers, reading buffer content, and saving changes. Integrates with Emacs' buffer management to ensure consistency.
Exposes Emacs' buffer and file operations through MCP, allowing external tools to interact with Emacs buffers as if they were local files, with full integration into Emacs' buffer management system
More integrated than file-system-only approaches because it can access Emacs buffers that may not be saved to disk, and respects Emacs' buffer modes and encoding settings
elisp-code-navigation-and-definition-lookup
Medium confidenceEnables jumping to function and variable definitions by resolving symbols to their source locations in the Emacs codebase or loaded packages. Uses Emacs' native find-function and find-variable mechanisms combined with source file indexing to map symbols to file paths and line numbers. Exposes this via MCP to support IDE-style 'go to definition' workflows.
Leverages Emacs' built-in find-function and find-variable commands which have deep knowledge of the Emacs installation and package load paths, rather than implementing custom symbol resolution
More reliable than generic language server approaches because it uses Emacs' native symbol resolution which understands autoload directives, package load order, and Emacs-specific conventions
elisp-syntax-checking-and-error-detection
Medium confidencePerforms static analysis and runtime validation of elisp code to detect syntax errors, undefined variables, and common mistakes. Combines byte-compilation (via Emacs' native byte-compiler) with custom linting rules to catch issues like unused variables, incorrect function calls, and type mismatches. Reports diagnostics via MCP in LSP-compatible format for integration with editor linters.
Integrates Emacs' native byte-compiler as the primary validation engine, which understands elisp semantics deeply, combined with custom linting rules that catch Emacs-specific anti-patterns
More accurate than generic linters because it uses the actual Emacs byte-compiler which understands elisp's dynamic nature, and more comprehensive than simple regex-based checkers because it performs semantic analysis
elisp-refactoring-rename-and-extract
Medium confidenceSupports automated refactoring operations like renaming functions and variables across multiple files, and extracting code into new functions. Works by analyzing the symbol table to find all references to a symbol, then applying transformations while respecting scope and shadowing rules. Uses buffer manipulation and file I/O to apply changes atomically.
Performs refactoring by analyzing Emacs' live symbol table and scope rules, ensuring that shadowed variables and local bindings are handled correctly, rather than using simple text-based search-and-replace
More accurate than text-based refactoring tools because it understands elisp's scoping rules and can distinguish between different symbols with the same name in different scopes
elisp-interactive-evaluation-and-repl-integration
Medium confidenceEnables executing elisp code snippets directly within the Emacs session via MCP, with results returned to the client. Supports evaluating expressions, loading files, and inspecting the state of the running Emacs instance. Integrates with Emacs' eval function and provides access to the current environment (variables, functions, buffers).
Provides direct access to the running Emacs process via MCP, allowing evaluation in the actual environment where code will run, rather than simulating execution in a separate sandbox
More powerful than static analysis because it can test code in the actual Emacs environment with all loaded packages and configurations, but requires careful handling of side effects
elisp-package-and-dependency-management
Medium confidenceAnalyzes elisp code to extract package dependencies, version requirements, and load-path configuration. Parses require and use-package declarations to build a dependency graph, then validates that all dependencies are available and compatible. Integrates with Emacs' package management system (package.el) to check installed versions.
Analyzes both static require/use-package declarations and queries the live Emacs package system to validate that dependencies are actually installed, combining static and runtime analysis
More accurate than parsing Package-Requires headers alone because it also detects dynamic requires and validates against the actual installed packages in the Emacs session
elisp-test-discovery-and-execution
Medium confidenceDiscovers and executes elisp unit tests by scanning for test functions (typically named test-* or *-test) and test frameworks (ert, buttercup, etc.). Parses test definitions to extract test names and metadata, then runs tests via the framework's API and collects results. Returns test results in a structured format compatible with IDE test runners.
Integrates with multiple elisp test frameworks (ert, buttercup) via a unified interface, auto-detecting which framework is in use and adapting test discovery and execution accordingly
More flexible than framework-specific runners because it supports multiple test frameworks and auto-detects which one is in use, rather than requiring manual configuration
elisp-documentation-generation-from-code
Medium confidenceGenerates documentation (markdown, HTML, or plain text) from elisp source code by extracting docstrings, function signatures, and variable definitions. Parses code structure to build a documentation outline, then formats it for human consumption. Supports custom templates and styling for different output formats.
Extracts documentation from both docstrings and code structure, using elisp's native documentation conventions (docstring format, function signatures) to produce accurate and complete documentation
More accurate than generic documentation generators because it understands elisp-specific conventions like docstring format and function signature syntax
elisp-macro-expansion-and-analysis
Medium confidenceExpands elisp macros to show their generated code, enabling developers to understand what code a macro produces. Uses Emacs' macroexpand and macroexpand-all functions to recursively expand macros, then formats the result for readability. Supports stepping through macro expansion to see intermediate steps.
Uses Emacs' native macroexpand functions which understand the full elisp macro system, including special forms and compiler macros, rather than implementing custom macro expansion logic
More accurate than custom macro expansion because it uses the actual Emacs macro expander which handles all edge cases and special forms correctly
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with elisp-dev-mcp, ranked by overlap. Discovered automatically through the match graph.
@upstash/context7-mcp
MCP server for Context7
cclsp
MCP server for accessing LSP functionality
cclsp
MCP server for accessing LSP functionality
MiniMax: MiniMax M2.1
MiniMax-M2.1 is a lightweight, state-of-the-art large language model optimized for coding, agentic workflows, and modern application development. With only 10 billion activated parameters, it delivers a major jump in real-world...
codemirror-mcp
** CodeMirror extension that implements the Model Context Protocol (MCP) for resource mentions and prompt commands.
mcp_sse (Elixir)
** An SSE implementation in Elixir for rapidly creating MCP servers.
Best For
- ✓Emacs Lisp developers building extensions and configurations
- ✓Emacs package maintainers working on complex elisp codebases
- ✓Users customizing their Emacs environment with elisp
- ✓Emacs Lisp developers needing inline documentation and type hints
- ✓Tool builders creating IDE features for Emacs (linters, formatters, documentation generators)
- ✓Package maintainers documenting elisp APIs programmatically
- ✓Tool builders creating IDE features that need to interact with Emacs buffers
- ✓External tools that need to manipulate Emacs files and buffers
Known Limitations
- ⚠Completion accuracy depends on proper elisp syntax in the buffer — malformed code may reduce suggestion quality
- ⚠No cross-file symbol resolution — only completes symbols visible in current buffer and loaded packages
- ⚠Performance degrades on very large buffers (>10k lines) due to full AST re-parsing on each keystroke
- ⚠Docstring extraction only works for functions that have been loaded into Emacs — unloaded code requires static parsing which may miss runtime-generated functions
- ⚠Anonymous functions and lambdas have no docstrings by design — only named functions are documented
- ⚠Macro expansion and generated code may not have source locations, making signature extraction unreliable
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
** - elisp (Emacs Lisp) development support tools, running in Emacs.
Categories
Alternatives to elisp-dev-mcp
Are you the builder of elisp-dev-mcp?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →