Skip to content
Twozero Docs
Sign in
Download
Twozero Docs

KEEP IT RUNNING

Agent can't see TD

Five checks, from the most common cause to the rarest.

In the plugin MCP

On this page 7

1. Was the chat opened before TouchDesigner?

An agent connects to twozero when its chat starts. If no TouchDesigner was running yet (say, the first start after a reboot), that chat may never see the twozero tools, and reconnecting from inside it does not help. With TouchDesigner fully loaded, open a new chat and ask whether the twozero_td tools are there.

2. Is the server running?

Look at MCP in TD's top bar: hover it for the server's state, click it to start the server. To have it start with TouchDesigner: Settings → AI & MCP → Auto start (or RMB on MCP → auto start MCP).

3. Does the server answer?

In a terminal:

bash 
curl http://localhost:40404/

The answer, shortened:

json 
{"hub": true, "instances": {"127.0.0.1_91778": {"project": "myProject.toe", "port": 49891, "ops": 240}}}

Use your own port if you changed it in Settings. JSON back means the server is running; its instances list should not be empty, which means your TouchDesigner is attached. *Connection refused* means it never started: check that twozero is running in TD and that nothing else holds the port.

4. Is the agent's config right?

  • Settings → AI & MCP → Reconnect agents: the wizard shows which agents are connected and can write the entry again.
  • In Claude Code: /mcp → twozero_td → reinitialize.
  • Changed the Port? The agent still points at the old one. In the wizard DISCONNECT the agent, then CONNECT it again.
  • The wizard showing CONNECTED only means the config file is right, not that a chat is connected right now.

5. It worked and then stopped?

TouchDesigner may be busy: a dialog waiting for an answer (an unsaved-changes or overwrite prompt is the usual one) or a long cook. Check the TouchDesigner window. The server answers, but nothing happens until TD is free.

Several TouchDesigners

Every open TouchDesigner registers with the one server on your port, so your agent needs one entry only. When several are open, the agent lists them and asks which one to work in.

Still stuck

Ask in Discord with your system, TouchDesigner build, plugin version and the agent you use. Known open problems, mostly on Windows 11, are on GitHub.