Docs

Editors and coding agents

How editors and coding agents that support MCP use Emolysis: setup buttons, ready-made configs and skills, and what your tool sends to its model.

Planned reference

Updated Oct 23, 2026

Docs menu · 25 pagesEditors and coding agents

Status

In private development. Early access by invitation. The names, options and formats on this page can change before the first release.

On this page

If you already work in an editor or coding agent that supports MCP, Emolysis plugs into it with one configuration entry. That tool then gains the platform profiles, templates and golden tests, and drives the same commands as the desktop app.

What the setup looks like

  1. Connect a platform in the app or with emo connect.
  2. Add the configuration entry for emo mcp to your tool; setup buttons on the web dashboard that write it are planned.
  3. Restart the tool. The Emolysis tools appear next to its own.

The entry itself is small: it starts emo mcp as a local process. See The MCP server for the entry and for tool names.

What the tool can do

Everything the engine can do, because each command, except the machine-token commands, is one tool. A few higher-level requests come as ready-made skills, so you do not have to spell them out:

  • a dashboard from a question,
  • a pipeline for a shape,
  • connecting a platform,
  • moving a table to another platform (planned), and
  • explaining a pipeline's lineage and cost.

The tools need an Emolysis account, as every use of Emolysis does, local files included; the Free plan is one. Sign in once in the app or with emo login in a terminal, or confirm the short code a tool returns in the browser when you are not signed in.

What exists today

The setup configs and skills are public on GitHub in emolysis/integrations, under the MIT license. They run on the Emolysis engine. Do not trust a download or package that says it connects an editor to Emolysis before we announce a release.

What your tool sends to its model

Your editor or coding agent sends tool results to its own model provider, under its own terms, and those results can include schemas, query results and sample values. Point it at tables you are comfortable sharing that way. See Data handling.

Not decided yet

  • Which editors and coding agents get a setup button first.
  • Whether each has a rules file or only the configuration entry.

The MCP server, The emo CLI and Model Context Protocol in the glossary. The integrations page shows every way to reach Emolysis.