Set up Logic Conductor

Setting up Logic Conductor has two parts. Your administrator installs it for one Dataverse environment and lists the projects it exposes. You, as the designer, decide which blocks, flows and business processes in those projects become tools, by turning on Expose as MCP Tool.

For administrators

To deploy Logic Conductor and set the projects it exposes, see Deploy Logic Conductor.

Before you begin

Requirement	Notes
Logic Composer	Installed in the environment.
Process Orchestrator	Optional. Needed only to expose business processes.
An MCP-capable AI client or agent	For example GitHub Copilot, Claude, Visual Studio Code or your own agent.
Access granted by your administrator	Your administrator decides who can connect. Every call runs with the caller’s own Dataverse permissions.

What your administrator configures

Setting	What it does	Notes
Environment	The Dataverse environment whose logic Conductor runs.	One installation per environment.
Project names	The projects whose exposed artifacts become tools, separated by commas or semicolons, for example Sales; Service.	Use project names exactly as they appear in Logic Fabric. With one project, tool names have no prefix; with several, each tool name starts with its project name.
Sign-in	How callers sign in. With per-user sign-in, every tool runs as the person asking.	Recommended for every shared installation.

Tool names change with the project list

Adding a second project to Project names adds the project prefix to every tool name, for example approve_credit_limit becomes sales_approve_credit_limit. Agents or prompts that call tools by name need updating. If you expect to expose more projects later, start with more than one.

Mark artifacts as tools

1. Open the logic block, logic flow or business process in a project that Conductor exposes.
2. Give it a clear name, title and description, and describe every input and output. These become what the AI sees. See Best practices.
3. Turn on Expose as MCP Tool and save.
4. Ask your administrator to restart Logic Conductor. Conductor builds its list of tools when it starts, so tools you add or change appear after a restart.
5. In your AI client, refresh the tool list and check that the new tool is there.

Expose as MCP Tool is independent of Expose as Dataverse Action. You can turn on either, both or neither. See Expose logic to AI and APIs.

Connect an AI client

1. Ask your administrator for the Logic Conductor address for the environment.
2. In your AI client, add an MCP server of type HTTP with that address. Name it after the environment, such as logic-conductor-prod.
3. Sign in with your organization account when the client asks.
4. Check the tool list. You should see one tool per exposed artifact, and nothing else.

Troubleshooting

Symptom	What to check
A tool is missing	Expose as MCP Tool is on and saved, the project is in Project names, and Conductor has been restarted since the change.
A tool still has its old name or inputs	Conductor hasn’t been restarted since the change.
A call fails with a permissions error	The signed-in user lacks the Dataverse privileges the block or flow needs.
start_… tools are missing	Process Orchestrator is installed and the business process has Expose as MCP Tool turned on.

Related

• How Logic Conductor works
• Logic Conductor best practices
• Set up Logic Foundry