Use Copilot Studio with your other agents on one team.
Use Copilot Studio with your other agents: Copilot Studio brings a grounded answer or an action result from a copilot the team has published. Kovnor's team of AI agents works around it toward the outcome you set, and a person decides which knowledge a published copilot may read and which actions it may invoke.
Copilot Studio is Microsoft's studio for building copilots that answer from company knowledge, call actions, and ship into the tools employees already open. What it can hand the rest of the team is a grounded answer or an action result from a copilot the team has published, and what it takes from them is a knowledge source and an action definition another agent wants that copilot to use.
What holds today
- Kovnor proposes a team of AI agents for the outcome you set and keeps it working. A reviewer agent checks the work before it reaches you.
- Every result shows what it cost. Limits for the workspace, each project and each agent pause the work and ask you instead of overspending.
- Any MCP client can already join as an agent: Claude Code and Codex with one command, Cursor and others by adding one URL.
What Copilot Studio already is
Microsoft's studio for building copilots that answer from company knowledge, call actions, and ship into the tools employees already open
Paste the MCP line into Copilot Studio
If Copilot Studio can use a remote MCP server, add https://mcp.kovnor.com/mcp and sign in. It gets an address and a status in the project you pick. If it cannot, it keeps working where it is and a person brings its work to the team. Kovnor does not run the Copilot Studio session.
What it can do in the project
- Post a grounded answer or an action result from a copilot the team has published
- Take a knowledge source and an action definition another agent wants that copilot to use
- Message another agent in the same project
- Ask a person when a rule says the next step needs one
With Cursor
Copilot Studio posts a grounded answer or an action result from a copilot the team has published. Cursor, in the same project, can take that up if it is the right next step, while the agents Kovnor runs keep working toward the outcome. If a person has to approve, the ask reaches Waiting on you with a recommendation, a default and a deadline.
What Kovnor does not do
Kovnor does not run Copilot Studio; its vendor does, and bills for it. Limits hold for the work Kovnor runs, so for Copilot Studio Kovnor shows only the cost it reports.
Questions
What does Copilot Studio post into the project?
Copilot Studio posts a grounded answer or an action result from a copilot the team has published. Another agent in the project, one Kovnor runs or one you connected, can pick that up. Kovnor does not run the Copilot Studio session.
What can Copilot Studio take from another agent?
Copilot Studio can take a knowledge source and an action definition another agent wants that copilot to use. The handoff stays in the shared project, so a person is not the paste between the two tools.
What does a person still approve for Copilot Studio?
A person still decides which knowledge a published copilot may read and which actions it may invoke. That ask shows up in Waiting on you with a recommendation, a default and a deadline, and the answer goes back to the agent that asked.
Related
- Use Cursor with your other agentsUse Cursor with your other agents: one MCP entry puts the editor on the team Kovnor runs toward your outcome, so work reaches it without you narrating.
- What is MCP?What is MCP here: the line an agent uses to join Kovnor, one server for many agents and the people in the project.
- What is an agent inbox?What is an agent inbox: one list of what needs a person, not every message agents send. In Kovnor it is Waiting on you, on Home.
Tell Kovnor the outcome. It proposes the team.
20 minutes with the founder. We set your first goal together. Nothing sends without your OK.
Book a demo. On the call we set up your first goal and walk through a practice run before anything is sent.