An entire data team. One download. Emolysis is the agentic lakehouse for data engineering and analytics. Direct a team of agents from your laptop to investigate business questions, develop dashboards, and build and test pipelines for your data platform.
This repository holds its client integrations. Everything here is a thin layer over one
MCP server, emo mcp, which ships with the Emolysis CLI (emo). This repository
contains no engine code.
Fresh scaffold (October 2026). The configs, the Claude Code plugin and the npm shim are written and tested here, but the Emolysis CLI is not publicly released yet, so these integrations have nothing to talk to until it is. The skills are written against planned command ids and check what the installed CLI provides; expect changes once the CLI is released. Nothing is published to npm, PyPI or the GitHub Marketplace yet. See ROADMAP.md.
| Path | What |
|---|---|
.claude-plugin/marketplace.json |
Claude Code marketplace emolysis |
claude-code/ |
Claude Code plugin emolysis: the MCP server plus five skills |
cursor/ |
Cursor MCP config and a project rule |
codex/ |
Codex config.toml snippet |
packages/mcp-shim/ |
@emolysis/mcp: npm launcher for emo mcp (not published yet) |
github-action/ |
Emolysis checks (preview) composite action (not yet available) |
docs/ |
Architecture, development and contributing guides |
Every client needs the Emolysis CLI (emo) on PATH.
Not yet available: the CLI is not released, and how it will be distributed is not
decided yet. This repository assumes uv tool install emolysis for now, which may change.
Emolysis has not published a package under that name (nor @emolysis/mcp on npm): do not
install anything under these names until this README says they are released. Until then
the client setups below install, but their server has nothing to start.
Without an Emolysis account the server works on local files with DuckDB. Connecting a platform or publishing a dashboard asks you to sign in.
/plugin marketplace add emolysis/integrations
/plugin install emolysis@emolysis
On Claude Code 2.1.275 or later, one step does both:
/plugin install emolysis --marketplace emolysis/integrations
The plugin starts emo mcp and adds five skills: /emolysis:dashboard,
/emolysis:pipeline, /emolysis:connect, /emolysis:migrate and /emolysis:explain.
See claude-code/README.md.
Copy cursor/mcp.json to .cursor/mcp.json in your project (or merge
its emolysis entry into ~/.cursor/mcp.json), and copy
cursor/rules/emolysis.mdc to .cursor/rules/emolysis.mdc.
See cursor/README.md.
codex mcp add emolysis -- emo mcpor add the table in codex/config.toml to ~/.codex/config.toml.
See codex/README.md.
Run emo mcp as a stdio server:
{ "mcpServers": { "emolysis": { "command": "emo", "args": ["mcp"] } } }Not yet available: clients that prefer to launch servers through npm will be able to use
npx -y @emolysis/mcp once the shim is published; it finds emo (or EMO_BIN) and runs
emo mcp. Do not run it before then.
The server exposes each Emolysis engine command as one MCP tool, named after the command
id with the dot replaced by an underscore: engine.doctor is engine_doctor. Call
engine.commands to list what your installed version provides. The skills and the Cursor
rule check that list first and say so when a command they need is not available yet.
task setup # pnpm install --frozen-lockfile
task gate # format check, config checks, actionlint, typecheck, tests, build, plugin validationNeeds Node 22+, pnpm 10, Task and uv (for actionlint). See docs/development.md and docs/contributing.md.
The code is MIT licensed (LICENSE). The license does not cover the Emolysis name or logo; see NOTICE.