Copilot Studio

com.microsoftPublished by microsoft.comv1.0.2Updated Oct 24, 2026

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

The publisher's own server: Microsoft Learn MCP

Overview

AI-generated overview

Microsoft Copilot Studio MCP lets an assistant create, configure, test, deploy and monitor Copilot Studio agents and workflows from an MCP client.

What you can do
  • Discover connector operations, schemas, existing connections and attachable resources
  • Manage agent inventory, draft authoring, lifecycle, sharing, previews and evaluation suites
  • Manage workflow inventory, draft authoring, lifecycle, real tests and run diagnostics
  • Read historical agent or workflow credit consumption and current environment credit capacity
  • Read Copilot Studio guidance skills and schemas before authoring
When to use it
Useful when you work in Microsoft Copilot Studio and want an assistant to help build, test, deploy or monitor agents and workflows, or check credit usage, without switching to the web portal.
Requirements
Runs locally via npx from the npm package @microsoft/copilot-studio-mcp; needs Node.js 22.18 or later (24 LTS recommended), an MCP-compatible client such as GitHub Copilot CLI or VS Code, and a Microsoft work account with access to a Copilot Studio environment. Sign-in and environment selection happen through the hosted service; no environment variables or headers are declared.
Before you install
Signing in ties the server to your identity and environment permissions, so the assistant can act with your access. Agent and workflow tools can author drafts, publish, share and run tests, which changes data in your environment. In organizations requiring FedRAMP High, the GitHub Copilot harness agent turns off at runtime to prevent data egress.

Installation

In SourceWeft

  1. Open Copilot Studio in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

Source: README.md at commit 5f9cecd

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v1.0.2LatestOct 19, 2026
  2. v1.0.1Oct 17, 2026
  3. v1.0.0Oct 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Microsoft integrations