Odel
MCP server: One MCP server.

Copilot Studio

@microsoftMCP server · External

A single entry point for working across the Copilot Studio agent and automation lifecycle.

Chatbot buildingv1.0.2MIT
Freeno charge per call
How to install

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: creates or changes data: records, files, settings.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npm@microsoft/copilot-studio-mcpv1.0.2

Run

npx -y @microsoft/copilot-studio-mcp

MCP client config

{
  "mcpServers": {
    "copilot-studio": {
      "command": "npx",
      "args": [
        "-y",
        "@microsoft/copilot-studio-mcp"
      ]
    }
  }
}
README3 min read

Copilot Studio MCP

Microsoft Copilot Studio MCP brings Copilot Studio tools into Model Context Protocol (MCP)-compatible CLIs, developer tools, and agentic interfaces. It provides a single entry point for working across the agent and automation lifecycle, from creation and configuration to testing, deployment, monitoring, and ongoing management.

This repository hosts the source for the MCP server. The server itself is published and installed from the npm package @microsoft/copilot-studio-mcp. It's also discoverable through the GitHub MCP Registry and the official MCP Registry.

Your client launches this package with npx. The server connects to Copilot Studio's hosted service after you sign in and select an environment, so access stays tied to your identity, environment permissions, and organizational policies.

Notice

If your organization requires Federal Risk and Authorization Management Program (FedRAMP) High compliance, the GitHub Copilot harness agent turns off at runtime to prevent data egress from the FedRAMP High compliance boundary.

Prerequisites

  • Node.js 22.18 or later (Node.js 24 LTS recommended)
  • A working MCP-compatible client: GitHub Copilot CLI, Visual Studio Code, or another MCP-compatible host
  • A Microsoft work account with access to a Copilot Studio environment

Install

Configure your client to launch the package with:

powershell
npx -y @microsoft/copilot-studio-mcp@latest

The client starts the server process and communicates with it over standard input/output (stdio). The package handles the connection to the hosted Copilot Studio service; you don't enter a remote MCP URL or clone this source repository. You can also install the server directly from the GitHub MCP Registry or a supported client's MCP gallery (for example, VS Code's @mcp/"Browse MCP Servers" gallery) and follow the listing's installation option for your client.

Available tools

After you sign in and select an environment, the server makes the connected service's tools available. The service catalog includes the following tools. Connection and sign-in utilities are separate.

ToolDescription
discover_resourcesDiscover connector operations and schemas, existing connections, dependent parameter values, and attachable resources.
get_consumptionRead historical agent or workflow credit consumption, or current environment credit capacity.
manage_agentsManage agent inventory, complete draft authoring, lifecycle, published-agent sharing, saved-draft previews, and agent evaluation suites and runs.
manage_workflowsManage workflow inventory, complete draft authoring, lifecycle, real tests, and run diagnostics.
get_copilot_studio_skillsStart here for Copilot Studio guidance. Read the matching core skill before authoring, then read schema.json.

The management, discovery, and consumption tools expose individual operations through action and parameters. The current tool schemas identify the advertised actions and their inputs. To read the focused contract and side-effect information for an action before you construct unfamiliar arguments, use discover_resources with action=describe_actions.

Troubleshooting

If setup fails, stop and report the error without sharing credentials or configuration JSON. DNS, refused/reset connections, and network timeouts have distinct safe cause codes. Check endpoint availability and network/proxy settings before an explicit retry; another call does not repair missing environment routing.

See SUPPORT.md for how to get help with this project.

Security

See SECURITY.md for how to report security issues.

License

Licensed under the MIT License.

Similar modules

Browse Chatbot building