Copilot Studio — MCP server for Claude Code and other clients
Brings Copilot Studio tooling into MCP-compatible clients: agents, workflows, credit usage. Requires a Microsoft work account with access to a Copilot Studio environment.
claude mcp add copilot-studio -- npx -y @microsoft/copilot-studio-mcpWhat Copilot Studio does
The server is one entry point into the Copilot Studio agent and automation lifecycle — authoring, configuration, testing, deployment, monitoring and day-to-day management. Once you sign in and pick an environment, your client sees the tools of the connected service.
Five tools ship with it. discover_resources surfaces connector operations and schemas, connections that already exist, values of dependent parameters, and resources you can attach. get_consumption reports past credit spend by agents or workflows, plus the current capacity of the environment. manage_agents and manage_workflows cover inventory, draft authoring, lifecycle, publishing, real tests and run diagnostics. get_copilot_studio_skills is the starting point for guidance: read the matching core skill first, then schema.json. Individual operations inside these tools are reached through action and parameters; before building unfamiliar arguments, ask discover_resources with action=describe_actions for the focused contract and side effects.
Node.js 22.18 or later is required, with Node.js 24 LTS recommended, along with a Microsoft work account that can reach a Copilot Studio environment. Your client launches the package through npx and talks to it over stdio, so there is no remote URL to enter. Under a FedRAMP High requirement the GitHub Copilot harness agent switches off at runtime to keep data inside the compliance boundary.
What it helps with
- see which operations and schemas a connector exposes
- check how many credits agents burned over a period
- take an agent draft through publishing
- run workflow tests and read the diagnostics
- read the core Copilot Studio skill before authoring
Example prompts for the agent
- Use
discover_resourcesto list the operations on this connector and describe their contract - How many credits did the environment consume last month?
- Publish the agent draft and show me the check result
How to install Copilot Studio
Platform CLI
claude mcp add copilot-studio -- npx -y @microsoft/copilot-studio-mcpPlatform CLI
codex mcp add copilot-studio -- npx -y @microsoft/copilot-studio-mcpConfig file
{
"mcpServers": {
"copilot-studio": {
"command": "npx",
"args": [
"-y",
"@microsoft/copilot-studio-mcp"
]
}
}
}Config file
{
"servers": {
"copilot-studio": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@microsoft/copilot-studio-mcp"
]
}
}
}Platform CLI
gemini mcp add copilot-studio npx -y @microsoft/copilot-studio-mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Copilot Studio
How do I install Copilot Studio in Claude Code?
Run claude mcp add copilot-studio -- npx -y @microsoft/copilot-studio-mcp. The client starts the package and communicates with it over stdio.
What does the Copilot Studio MCP server do?
It exposes Copilot Studio tooling to an MCP-compatible client: resource discovery, credit consumption, agent and workflow management, and skill guidance.
What do I need before it works?
Node.js 22.18 or later, an MCP-compatible client, and a Microsoft work account with access to a Copilot Studio environment. Access follows your identity, environment permissions and organizational policies.
