Microsoft Copilot setup guide
Connect Microsoft Copilot to ClawCall with remote MCP
Add ClawCall to a Copilot Studio agent with the MCP onboarding wizard and OAuth dynamic discovery. Developers can also add it to GitHub Copilot in VS Code; consumer Copilot chat does not offer this setup.
https://api.clawcall.dev/mcp- Setup surface
- Copilot Studio MCP onboarding wizard
- Transport
- Streamable HTTP
- Authentication
- OAuth 2.0 dynamic discovery
Before you start
mcp.json and its Auth CodeLens.- Access to Copilot Studio, with permission to add tools to an agent.
- A ClawCall account.
- A real US destination in +1 E.164 format for any call you choose to place.
- A clear, user-directed task with destination and decision boundaries specified before a real call.
Connect Microsoft Copilot to ClawCall
Open the correct Copilot surface
Open the target agent in Copilot Studio. Consumer Copilot chat does not offer this setup.
Start the MCP onboarding wizard
Open Tools, choose Add a tool, select New tool, and choose Model Context Protocol.
Enter server details
Set Server name to ClawCall, describe it as a user-directed US phone-call tool, and set Server URL to
https://api.clawcall.dev/mcp.Server URL: https://api.clawcall.dev/mcpChoose OAuth dynamic discovery
Select OAuth 2.0, then Dynamic discovery. ClawCall publishes authorization metadata and supports Dynamic Client Registration, so manual endpoints and a static secret are unnecessary.
Create the connection
Select Create, then create a new user connection. Complete ClawCall sign-in and approve
calls:readandcalls:write.Add ClawCall to the agent
Select Add to agent. Review the discovered eleven tools and confirm Power Platform policies do not block the connector.
Always allow every ClawCall tool
Where the tenant offers per-tool or agent-level approval controls, set all ClawCall tools to Always allow or its closest equivalent.
Test before publishing
Run
get_balancein the test pane without calling. Then use a number you control, inspect captured transcript evidence when present, and only publish the agent after the controlled test passes.Or use GitHub Copilot in VS Code
In VS Code, run MCP: Add Server from the Command Palette, choose HTTP, enter the ClawCall URL, and save the server as clawcall. In
mcp.json, use the Auth CodeLens to complete OAuth, then confirm the tools in Copilot Chat. This is separate from consumer Microsoft Copilot.
OAuth scopes and host permissions
Microsoft Copilot signs in with OAuth and asks for two scopes: calls:read to read account and call state, and calls:write to place or hang up calls and change call settings. It gets revocable tokens, never your ClawCall API key.
Recommended: Always allow every ClawCall tool
Set every ClawCall tool to Always allow, or the closest control your tenant approves, so the agent can run the complete calling workflow. Your tenant’s data policy still decides what is permitted.
Always allow only skips the repeated approval prompts. It does not widen the two OAuth scopes, override tenant policy, or allow bulk or automated calling.
Verify read-only, then place one controlled call
Check account state first. Only after that succeeds, place the first real call to a number you control.
Check my ClawCall plan and remaining trial allowance. Do not place a call.
Using ClawCall, call my phone at +1XXXXXXXXXX. Say this is a connector test, ask me to confirm I can hear the AI, then end the call. Show me any transcript evidence actually captured afterward.
Tools and troubleshooting
ClawCall gives Microsoft Copilot 11 tools: read tools for the calling guide, your plan, settings, calls, transcripts, and recordings, and write tools that place, wait on, or hang up a call and update settings. A call’s outcome describes the phone network, so read the transcript evidence actually captured before treating the task as done. The remote MCP reference lists every tool and scope.
If no tools appear, check that the server URL ends in /mcp. If you see 401 or a sign-in prompt, reconnect and approve ClawCall again instead of pasting an API key. For anything else, see troubleshooting in the docs.
Disconnect and revoke access
- Disconnect or remove ClawCall in Microsoft Copilot.
- Open ClawCall Dashboard → Settings → Connected AI assistants → Disconnect to revoke its OAuth tokens.
FAQ
- Do I need to choose ClawCall before every request?
- No. Once the connection is enabled, the agent can pick ClawCall automatically when an ordinary request needs a phone call. Naming the tool is optional and mainly useful for troubleshooting.
- What does it cost?
- The ClawCall trial includes 30 calls and 30 minutes, whichever lasts later. After that, a paid plan covers ongoing calls. The host itself may need its own plan for plugins or connectors.
- Does a successful network outcome prove the task succeeded?
- No. A network outcome describes the call path. Read the transcript evidence actually captured before claiming a reservation, cancellation, price, or other real-world task was completed.
- How do I revoke access?
- Remove or disconnect ClawCall in the host, then open ClawCall Dashboard → Settings → Connected AI assistants → Disconnect to revoke that connection’s tokens.
- How long does ClawCall keep transcripts and recordings?
- ClawCall deletes transcripts 7 days after a call ends and recordings 10 minutes after a call ends. Recording URLs are temporary and cannot be renewed after they expire.
Sources
Setup steps come from Microsoft Copilot’s own documentation and ClawCall’s product documentation, checked on the dates below.
- Microsoft: Connect an agent to an existing MCP server
- GitHub: Extend Copilot Chat with MCP servers
- Microsoft FY2026 Q4 earnings
- ClawCall: Hosted MCP for AI agents
- ClawCall security
Related pages
Give Microsoft Copilot a phone line
Create a ClawCall account, add the endpoint, and start with the read-only check. The trial includes 30 calls and 30 minutes, whichever lasts later.