Copilot Studio MCP

70/100

Capped at 70: core tools not tested (only setup or self-check calls passed); the tests add up to 88. Why scores are capped

Last tested 2026-11-11 (Fresh: tested within 30 days) Connects · tools listedNo tool call tested yet Connects without a key; tool calls need one

No advisories in range for tested 1.0.4 (checked 2026-11-11)

Security review: not tested

Test points add up to 88; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology

Test points before the cap (88/100)

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs10/15
  • License3/10

Tested npm @microsoft/copilot-studio-mcp 1.0.4 (published by Microsoft; the package has no license field or license file and names no repository). Stdio bridge to Microsoft Copilot Studio, 9 tools. copilot_studio_status (self-check) reported signedIn:false; copilot_studio_list_environments asked us to sign in first with copilot_studio_connect, a Microsoft account sign-in we don't do. Core tools not tested. Not labelled Official: we found no Microsoft page naming the package this run.
Tool-call test (2026-11-11, direct MCP stdio client, no LLM): fail. 0 of 1 function call passed; needs a Microsoft sign-in. Core tools not tested. Evidence: local test run, Nov 11, 2026.

Transport (tested 2026-11-11): stdio

Token cost (estimate): approx. 1525 tokens, cl100k estimate (9 tools, measured 2026-11-11, version 1.0.4). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 5 read, 4 write (state-changing), 0 unclassified · Auth: API key · Rate limit: unknown · Pricing unit: unknown

Auth: API key. Rate limit: unknown. Pricing unit: unknown.

  • copilot_studio_clear_read_cache — read
  • copilot_studio_connect — write (state-changing)
  • copilot_studio_connection_setup_status — read
  • copilot_studio_disconnect — write (state-changing)
  • copilot_studio_list_environments — read
  • copilot_studio_prepare_connection — read
  • copilot_studio_select_environment — write (state-changing)
  • copilot_studio_setup_connection — write (state-changing)
  • copilot_studio_status — read

listing-flags calls_need_key or auth_kind

Score 70/100 · Tools 9 · Token cost approx. 1,525 tokens · Compare · Last tested 2026-11-11 · Version tested 1.0.4 · Package @microsoft/copilot-studio-mcp

Summary: Copilot Studio MCP completed an MCP handshake without credentials and exposed 9 tools.

Evidence summary

Handshake
pass
Tools listed
9
Context cost
approx. 1525 tokens, cl100k estimate (9 tools, measured 2026-11-11, version 1.0.4; an estimate) ranking · add up your servers' context cost
API key
Connects without a key; tool calls need one
Tested
2026-11-11

Test results

TestResultPointsEvidence
installpass20npm install @microsoft/copilot-studio-mcp (Node 20, Linux) succeeded in 0s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 9 tools listed in 3.4s.
maintenancepass25Latest release published 0 days before test.
docspartial10README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package).
licensepartial3License not machine-detected as OSI (no license found).

Local-model readiness

Token cost (estimate): approx. 1525 tokens, cl100k estimate for 9 tools · about 19% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-11

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 9 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Checked on 2026-11-11 for version 1.0.4 against OSV, GitHub advisories. Scope: the package itself; dependencies not scanned.

No published advisories found in OSV and GitHub advisories for @microsoft/copilot-studio-mcp 1.0.4 as of 2026-11-11. This is not a security audit.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-11 test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

16ebf5df4f6c: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "@microsoft/copilot-studio-mcp",
  "version": "1.0.4",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-11",
  "tools_count": 9,
  "deprecated": false,
  "archived": null,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install @microsoft/copilot-studio-mcp` (Node 20, Linux) succeeded in 0s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 9 tools listed in 3.4s."
    ],
    "maintenance": [
      "pass",
      25,
      "Latest release published 0 days before test."
    ],
    "docs": [
      "partial",
      10,
      "README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "partial",
      3,
      "License not machine-detected as OSI (no license found)."
    ]
  }
}

Install

npx -y @microsoft/copilot-studio-mcp

Pin the version we tested

npx -y @microsoft/copilot-studio-mcp@1.0.4

tested 2026-11-11. Newer versions may differ and were not tested by us.

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

Tools listed

copilot_studio_clear_read_cache, copilot_studio_connect, copilot_studio_connection_setup_status, copilot_studio_disconnect, copilot_studio_list_environments, copilot_studio_prepare_connection, copilot_studio_select_environment, copilot_studio_setup_connection, copilot_studio_status

Tool history: captured Nov 11, 2026. All tool history.

Quick config

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

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run npm install @microsoft/copilot-studio-mcp (Node 20). This is the exact command we ran on 2026-11-11.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (9 in our test).
{
  "mcpServers": {
    "copilot-studio-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@microsoft/copilot-studio-mcp"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

FAQ

Is Copilot Studio MCP deprecated?

No. @microsoft/copilot-studio-mcp was not deprecated or archived when we last tested it on 2026-11-11.

What replaces Copilot Studio MCP?

Nothing; Copilot Studio MCP is not deprecated as of 2026-11-11.

Does Copilot Studio MCP need an API key?

It connects and lists 9 tools without a key, but its tool calls need one.

Embed the badge

TestedMCP: 70/100, tested 2026-11-11

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue