MODO
LEARN MODO / PRACTICAL GUIDE

Connect an agent through MCP

Experimental integration · setup requiredReviewed 2026-10-20
A guide to the current beta, not a release announcement.

These instructions are reviewed against the app source. Final-installer walkthroughs are still pending. Check platform availability and requirements before installing. Windows is an updates list, outside the 1,000 beta places.

MCP lets a compatible agent read project context and use the capabilities you allow. You can use MODO without an agent.

Connect the first agent

  1. Open the MCP control in the bottom toolbar.
  2. Enable Allow agent access.
  3. Under Connect an agent, choose your client and enter a distinct Agent name.
  4. Copy the generated configuration and merge it into the client's MCP settings, keeping its existing servers.
  5. Restart that client's MODO MCP server.
  6. Ask: “Read the MODO context and tell me the project name and revision without changing it.”
  7. Return to Connections and check the name, successful request and timestamp.

The MCP control lights up after a successful request. Merely enabling the switch or copying configuration does not mean a connection is working.

The generated local configuration uses this installation. Do not copy another person's executable paths. HTTP clients use individually scoped, expiring tokens; the token is shown once for copying. Store it in your client's secure configuration, not in the project.

Work with more than one agent

Enable Allow multiple agents at once, give each a distinct identity and separate tasks. For example, one can review content while another edits a named component.

Edits use project revisions and transactions. When an agent sees a conflict, it should read the current state before preparing a new change. Multiple agents do not make simultaneous edits to the same values conflict-free.

Keep control of access

The local bridge follows the local policy; HTTP tokens use their selected scopes. A request in natural language to “only read” is not a substitute for restricting permissions when you need enforced read-only access.

Pause agent access from the MCP panel, or revoke a specific HTTP token. Remote publishing and other protected actions still require their applicable confirmations.

You do not need to expose MODO's local daemon to the internet. Your agent provider may process the context it receives remotely: review that provider's settings before giving it confidential project material.

See MODO's local workflow and GitHub export.

Shared with the app’s offline Help · 0.1.0-alpha.1-docs.2
Need a correction? Tell us