Microsoft Copilot Studio
Give Microsoft Copilot Studio agents your ERP, CRM, databases and legacy systems through an engini MCP server, and call Copilot Studio agents from workflows.
Book a demoMicrosoft Copilot Studio for AI agents and workflows.
engini lets the agents your company builds in Microsoft Copilot Studio act in the systems Microsoft does not reach: add an engini MCP server as a tool, and the agent can read and write in SAP, NetSuite, Oracle, Salesforce, databases behind your firewall and more, with only the tools you allow and every call on record. The other way round, a workflow can start a conversation with a Copilot Studio agent, send it a message and use its answer. Connect from Copilot Studio over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log
in engini
What a workflow can do with Copilot Studio. And what your Copilot Studio agent can do through engini.
These tools let a workflow or another agent talk to a published Copilot Studio agent. What a Copilot Studio agent can do in your systems is the toolset of the engini MCP server you add to it.
Converse
Send a message to a Copilot Studio agent and wait for its answer.
Hold a longer conversation, one message at a time.
Close the conversation.
Read
Read the messages and cards the agent sent back.
Triggers
There are no Copilot Studio triggers. A Copilot Studio agent calls engini tools through MCP when it needs them, and a workflow calls the agent when it needs an answer.
Connect your AI agent to Microsoft Copilot Studio. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Microsoft Copilot Studio connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of Microsoft Copilot Studio tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects Microsoft Copilot Studio and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every Microsoft Copilot Studio tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to Microsoft Copilot Studio through engini
{
"mcpServers": {
"engini-microsoft-copilot-studio": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Microsoft Copilot Studio connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the Microsoft Copilot Studio tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build with Copilot Studio and engini. Agents in Microsoft 365 that reach every system.
An ERP agent in Teams
A Copilot Studio agent in Teams answers order, invoice and stock questions from SAP, NetSuite or Oracle through an engini MCP server with read tools only.
A service desk agent that acts
A Copilot Studio agent opens and updates ServiceNow incidents and checks accounts in Okta, through the tools its engini toolset allows.
Legacy systems in reach
A Copilot Studio agent reads from IBM i, SQL Server or SAP ECC behind the firewall, through engini's On-Prem Agent, with no inbound ports.
Your agent as a step
A workflow sends a customer email to a Copilot Studio agent, takes its answer and records it in Dynamics 365 or Salesforce.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Microsoft Copilot Studio and another system engini connects is available.
You decide what each agent may do in Microsoft Copilot Studio. engini enforces it on every call.
Only the tools you allow
A toolset lists the Microsoft Copilot Studio tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own Microsoft Copilot Studio account and engini acts as that person, with their Microsoft Copilot Studio permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
engini as the agent's tools, or the agent as a step.
As tools: create an MCP server in engini with the connections and tools a Copilot Studio agent may use, and add it to the agent as an MCP tool. The agent sees only those tools, engini keeps the credentials, and every call lands in History and the audit log.
As a step: publish the agent to the Direct Line channel and add a Copilot Studio connection in engini. A workflow or another agent can then ask it a question and use the answer.
Connect Microsoft Copilot Studio in three steps. Then decide what each agent may do.
Sign in to Microsoft Copilot Studio
For tools, create an engini MCP server and add its address to your Copilot Studio agent as an MCP tool. For the other direction, publish the agent to the Direct Line channel and add a Copilot Studio connection with its secret.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in Microsoft Copilot Studio from Claude, ChatGPT, Cursor or your own code.
Microsoft Copilot Studio and engini. Straight answers.
Can an AI agent write to Microsoft Copilot Studio, or only read?
Both. engini has tools to start conversations with a Copilot Studio agent and send it messages. What the agent can change in your systems is set by the engini MCP server you give it. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
How does a Copilot Studio agent reach SAP or NetSuite through engini?
Create an MCP server in engini with the SAP or NetSuite connection and only the tools the agent may use, then add it to the agent in Copilot Studio as an MCP tool. engini enforces the toolset on every call.
Do we need a Power Platform connector for each system?
No. One engini MCP server can carry tools for many systems, and you choose them per agent.
Can it reach systems behind our firewall?
Yes. Systems inside your network connect through the engini On-Prem Agent, which opens every connection itself, so there are no inbound ports.
Does the agent act as me in Microsoft Copilot Studio?
Through MCP, each call runs with the engini connection behind the tool and is recorded under the user. Through Direct Line, engini talks to the agent as a channel user.