emacs-runtime-mcp
Related Servers
Alternatives to emacs-runtime-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceIt enables local MCP clients to interact with the live Positron R or Python session, supporting variable inspection, silent evaluation, and state-changing execution.2MIT
- FlicenseNot gradedqualityDmaintenanceEnables agents to search and call ranked MCP servers and registered agents through one remote endpoint, delegate tasks, and use hosted tools without installation while keeping credentials per-call and unstored.-
- FlicenseNot gradedqualityAmaintenanceEnables organizations to administer remote MCP servers with function-level allow lists and credential modes, then let developers bundle permitted tools behind a single unified endpoint offering just two functions—search and execute—so agents dynamically discover and invoke only authorized tools with every call auditable.-
- FlicenseNot gradedqualityCmaintenanceEnables secure discovery and invocation of sandboxed filesystem, repository inspection, and utility tools through a unified MCP client with schema validation, timeouts, and execution traces.-
- AlicenseAqualityAmaintenanceLocalBridge MCP is a bridge between an online AI chats and your computer. Most online AI chats can reason, and write code, but they normally cannot touch the local files, terminals, and scripts that make real work happen. This gives a trusted assistant a controlled doorway into a machine you own, so it can inspect files, edit text, search a project, run tests, use Git, and operate a shell.173Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables security researchers and developers to run Kali Linux tools such as Nmap, nm, objdump, strings, and tshark through an MCP client, supporting network scanning, binary and symbol analysis, string extraction, traffic capture, and isolated Docker-based command execution.-
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. Its purpose—evaluating a single Emacs Lisp form—is unambiguous.
The single name 'emacs_eval' follows a clear namespace_verb convention in snake_case, which is readable and predictable. With only one tool there is no pattern to verify against, so it cannot be judged fully consistent.
A single tool is thin for a server whose stated scope is an Emacs runtime. It earns its place, but the surface is minimal enough that agents will hit its limits quickly.
Evaluation of one form at a time is functional but leaves notable gaps: no batch evaluation, no file loading or buffer inspection, and no way to explore server state. The core operation exists, but the surrounding lifecycle is largely absent.