Add the Microsoft Copilot Studio MCP server to Cursor

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

Scopes, env vars, OAuth and limits: Cursor MCP config guide

Cursor prompts you to sign in the first time a remote OAuth server is used. Microsoft Copilot Studio runs locally; set any credentials Microsoft asks for before starting Cursor.

Ask Cursor for something Microsoft Copilot Studio can do. Author, test, publish and monitor Copilot Studio agents and workflows from your own MCP client. Approve the first tool call and check the result before allowing write actions automatically.

• · Remote servers take a url; local servers take command and args.
• · Values can reference ${env:NAME} so secrets stay out of the file.

How do I add the Microsoft Copilot Studio MCP server to Cursor?

Run: { …. Cursor prompts you to sign in the first time a remote OAuth server is used.

Is this the official Microsoft Copilot Studio MCP server?

Yes. It is published by Microsoft as com.microsoft/copilot-studio in the official MCP registry.

Does the Microsoft Copilot Studio MCP server need an API key?

It runs locally from a package. See Microsoft's docs for any credentials it needs.