effect-house-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EH_PROJECT | No | Pins the kernel to the editor that has this project open, useful with several editors. | |
| EH_APP_PATH | No | App path. Default: /Applications/Effect House.app, or what the app recorded in its app.json. | /Applications/Effect House.app |
| EH_FRONT_PATH | No | Individual path to the Effect House front executable for non-standard installs or other systems. | |
| EH_SUPPORT_DIR | No | Individual support directory path for non-standard installs or other systems. | |
| EH_MCP_CACHE_DIR | No | Where the docs cache lives. | |
| EH_MCP_LOG_LEVEL | No | Log level: debug, info, warn or error. Logs go to stderr. | info |
| EH_MCP_STATE_DIR | No | Where the workspace copy lives. | |
| EH_EXECUTABLE_DIR | No | Individual path for non-standard installs or other systems. | |
| EH_WORKSPACE_TEMPLATE | No | Individual workspace template path for non-standard installs or other systems. | |
| EH_MCP_AUTOMATION_TOOLS | No | Set to 1 to also expose the editor's automation tools. Off by default. | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| instancesA | Find Effect House: the installation and version, every running editor instance (port, heartbeat, health), the project each one has open, the eh kernel state and the workspace folder. Call it first when a cell cannot reach the editor. |
| launchA | Open Effect House and wait until its automation server answers. With |
| docs_searchA | Search the official Effect House documentation at effecthouse.tiktok.com/learn (getting started, workspace objects and components, editor panels, Visual Scripting nodes, APJS API reference, tutorials, publishing). Matches page paths and, for pages already read or indexed, titles and text. Returns URLs to pass to |
| docs_readA | Read one official Effect House documentation page as Markdown. Accepts a full URL or a path under /learn/, for example |
| workspace_readA | Read a file or list a folder of the eh kernel workspace: AGENTS.md, flow/, skills/, APJS/ declarations, reference/, Planning/. Paths are relative to the workspace root, or absolute inside it. Use it when your client cannot read local files. |
| runA | Run a JavaScript cell in the Effect House eh kernel, which drives the open editor through a pre-connected (Bridge note: Effect House must be open. |
| resetB | Discard eh kernel state (session values and connection). |
| statusB | Report eh kernel status: cells run, instance, project and connection. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools are clearly distinct: docs_search/docs_read, workspace_read, launch, run, and reset each target a different action. The main overlap is between `instances` and `status`, which both report instance, project, connection, and kernel state, so an agent may hesitate between them. Descriptions provide enough guidance to recover, but the boundary is not perfectly sharp.
The set mixes bare verbs (`reset`, `launch`, `run`), bare nouns (`instances`, `status`), and prefixed action names (`docs_search`, `docs_read`, `workspace_read`). The prefixed group is consistent, but the overall convention varies across the surface. It remains readable, just not predictable.
Eight tools is well within the ideal 3-15 range for a focused editor-bridge server. Each operation maps to a meaningful lifecycle step: discover, launch, run, inspect, reset, and documentation/workspace access. No tool feels gratuitous, though `status` is somewhat redundant with `instances`.
The surface covers the core workflow for driving Effect House: locating/launching the editor, running kernel cells, checking status, resetting state, reading docs, and reading workspace files. Minor gaps exist around writing workspace files or managing projects directly, but most agents can work around those via `run` cells.