Embody MCP Server

Embody puts your ideas on screen as fast as you can describe them. Operators, connections, parameters, the works. Want to try a different direction?

Local serverstdioPython

What is the Embody MCP server?

Connect Embody to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Embody puts your ideas on screen as fast as you can describe them. Operators, connections, parameters, the works. Want to try a different direction? Spin up a new approach in seconds. Compare attempts side by side. Branch off the one that. The embody mcp server is what makes that connection.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • create_op — Create any operator type in any network
  • set_parameter — Set values, expressions, or bind modes on any parameter
  • connect_ops — Wire operators together
  • execute_python — Run arbitrary Python in TD's main thread
  • export_network — Export networks to diffable .tdn YAML
  • create_extension — Scaffold a full extension (COMP + DAT + wiring)
  • get_op_errors — Inspect errors on any operator and its children
  • Setup — 1. Pick an AI assistant in the Setup Wizard — it opens on first install, or re-run

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Embody's toolset — create_op, set_parameter, connect_ops and 5 more — is a fair guide to whether it matches your workflow. It is maintained by dylanroscover; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Embody's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
create_opCreate any operator type in any network
set_parameterSet values, expressions, or bind modes on any parameter
connect_opsWire operators together
execute_pythonRun arbitrary Python in TD's main thread
export_networkExport networks to diffable .tdn YAML
create_extensionScaffold a full extension (COMP + DAT + wiring)
get_op_errorsInspect errors on any operator and its children
Setup1. **Pick an AI assistant in the [Setup Wizard](https://dylanroscover.github.io/Embody/embody/setup-wizard/)** — it opens on first install, or re-run it anytime (the **Setup Wizard** pulse on the Embody COMP). Prefer par

How to install the Embody MCP server

{
  "mcpServers": {
    "envoy": {
      "type": "http",
      "url": "http://127.0.0.1:9870/mcp"
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Embody to create op.
  • Use Embody to set parameter.
  • Use Embody to connect ops.

Frequently asked questions

It connects Embody to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (create_op, set_parameter, connect_ops, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Embody directly.