MCP

What this connection is for

Use MCP to manage your Conduit apps from an AI assistant like ChatGPT or a coding agent you already use. The assistant can review your apps and help build new versions for Revit, AutoCAD, or ACC.

It serves a different purpose from Copilot, which works inside an open Revit model. It is also separate from an integration that your generated app uses to exchange data with an external platform.

Connect your agent

1. A workspace admin opens the workspace menu at the top left of Conduit.
2. Go to Workspace settings → Agent Access.
3. Name and create a token for the agent. Choose whether to enable Allow desktop deployment assignment. Read, plan, and generate access are included.
4. Copy the configuration for your AI assistant. Conduit hosts the MCP connection; you do not need to run a local MCP server.
5. Save the token in the protected host environment as CONDUIT_API_TOKEN, then reload your agent with that configuration.
6. Ask the agent to run whoami and use Agent Access to verify the connection to the intended workspace.

Give the agent the access required for its task. Store its token in the client’s credential configuration rather than putting it in a project brief or a shared conversation.

Approve the plan and desktop recipients

• Generation: approve the app plan before the agent launches a build.
• Desktop deployment: approve the intended recipients before assigning a Revit or AutoCAD app.

Review the app, version, and recipients each time the agent asks to deploy.

Generation uses the same credits as building through Conduit. Deploying an existing version does not spend generation credits.

Give the agent a complete app brief

“Use Conduit to plan a Revit tool that exports selected doors to CSV. Include element ID and Mark, keep the model unchanged, and present the plan for my approval before generating.”

Specify the target application, input scope, rules, output, and any changes the app may make. After the build, inspect the version and test it using the same process as an app created in the Builder.

If the agent cannot complete an action

Check that the connection is configured for the intended workspace and that the token has access to the requested action. For generation or desktop assignment, also check whether the required approval has been given.

Ask the workspace admin to review Agent Access when permissions need to change. If the issue persists, send the action name and error message through Help & feedback, leaving out the token.