3 ms·
Your GitHub link 404s. I wonder, why not just get ECA to run `emacsclient -e <elisp>` instead? Does that not work as well?
by skulk 6mo ago
Your GitHub link 404s.
I wonder, why not just get ECA to run `emacsclient -e <elisp>` instead? Does that not work as well?
- iLemming 6mo agoThank, you, I did't realize I forgot to make the repo public. Fixed it. Why MCP? `emacsclient -e` is the transport. The MCP is the transport plus quoting, output capture, error handling, timeouts, inline hints, screenshots, and tool-schema discoverability. You can reimplement all of that inside every LLM turn, but you pay for it in tokens, latency, and bug surface on every call. The MCP lifts that boilerplate out of the conversation once and never charges you for it again.