Microsoft · Codex
Add the Microsoft Copilot Studio MCP server to Codex
Author, test, publish and monitor Copilot Studio agents and workflows from your own MCP client.
1. Add the server
Run in your terminal
# ~/.codex/config.toml [mcp_servers.copilot_studio] command = "npx" args = ["-y", "@microsoft/copilot-studio-mcp"]
Scopes, env vars, OAuth and limits: Codex MCP config guide
2. Sign in
Run codex mcp login <name> to complete OAuth for a remote server. Microsoft Copilot Studio runs locally; set any credentials Microsoft asks for before starting Codex.
3. Try it
Ask Codex 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.
- · Each server is a [mcp_servers.<name>] table in config.toml.
- · Use enabled_tools or disabled_tools to keep the tool list short.
Get the weekly agent stack update
New official MCP servers, spec changes and harness releases, checked against the source. One email a week, no fluff.
FAQ
- How do I add the Microsoft Copilot Studio MCP server to Codex?
- Run: # ~/.codex/config.toml …. Run codex mcp login <name> to complete OAuth for a remote server.
- 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.
Links
Microsoft Copilot Studio in other clients
More ai & media for Codex
Work at Microsoft?
Feature Microsoft Copilot Studio across the directory and its category from $49/month.
Reviewed Oct 21, 2026. Command generated from the registry record and checked against Codex's documented syntax.