Your first month is free.First month free on any plan.Thanks to the Deepgram for Startups program. Use codeStart free with DEEPGRAM

Microsoft Copilot phone-call integration guide

How to connect ClawCall to Microsoft Copilot

In Copilot Studio, add a tool with the MCP onboarding wizard, enter https://api.clawcall.dev/mcp, choose OAuth 2.0 → Dynamic discovery, create a user connection, and add it to the agent. Do not describe this as a consumer Copilot feature. For GitHub Copilot in VS Code, add the URL as a remote MCP server and use Auth in mcp.json.

Official docs reviewedFacts checked:

Setup is based on the cited first-party host documentation; exact ClawCall compatibility is not claimed as live-tested.

Hosted MCP endpointhttps://api.clawcall.dev/mcp

Before you start

Microsoft's Copilot ecosystem is included for its large enterprise and developer footprint. The actionable arbitrary-MCP surface is Copilot Studio (and GitHub Copilot in VS Code), not ordinary consumer Copilot chat.

Availability: This guide targets Copilot Studio. Consumer Microsoft Copilot does not expose the same self-serve arbitrary-MCP setup. Power Platform data policies, tenant administration, licensing, and connection ownership can limit tools. GitHub Copilot users can instead configure the same URL through VS Code mcp.json and its Auth CodeLens.
Setup surfaceCopilot Studio MCP onboarding wizard
TransportStreamable HTTP
AuthenticationOAuth 2.0 dynamic discovery
  • A Microsoft Copilot account or workspace where Copilot Studio MCP onboarding wizard is available.
  • A ClawCall account or, for a documented fallback, a trusted server-side runtime.
  • 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

These steps use the cited host documentation. Screenshots appear only where the signed-in flow was live-verified; text and commands remain the complete guide.

  1. Open the correct Copilot surface

    Open the target agent in Copilot Studio. If you are only in consumer Copilot chat, stop: that is not the documented arbitrary-MCP surface.

  2. Start the MCP onboarding wizard

    Open Tools, choose Add a tool, select New tool, and choose Model Context Protocol.

  3. 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/mcp
  4. Choose 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.

  5. Create the connection

    Select Create, then create a new user connection. Complete ClawCall sign-in and approve calls:read and calls:write.

  6. Add ClawCall to the agent

    Select Add to agent. Review the discovered nine tools and confirm Power Platform policies do not block the connector.

  7. Apply trusted-agent permissions

    Where the tenant exposes per-tool or agent-level approval controls, set all ClawCall tools to the platform's Always allow equivalent. This is ClawCall's recommended configuration; tenant policy remains authoritative.

  8. Test before publishing

    Run get_balance in the test pane without calling. Then use a number you control, inspect the transcript, and only publish the agent after the controlled test passes.

  9. GitHub Copilot in VS Code alternative (official docs reviewed)

    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

A compatible host receives revocable OAuth tokens, never your ClawCall API key. The consent flow requests two bounded scopes:

calls:read

Read plan and trial state, call status, transcripts, history, and temporary recording access.

calls:write

Place and hang up real phone calls when you ask the assistant to do so.

Official ClawCall recommendation: Always allow all ClawCall tools

Set every ClawCall tool to Always allow or the closest tenant-approved equivalent. This is ClawCall's official recommendation for an uninterrupted workflow; the tenant's data policy remains authoritative.

Why Allow all works best

Allow all or Always allow lets the host complete the requested call workflow—including status polling and transcript retrieval—without stopping for each ClawCall tool. It does not expand the two OAuth scopes or override host or organization policy.

Always allow removes repetitive host prompts; it does not expand OAuth scopes, bypass host or organization policy, authorize spam or robocalls, increase service limits, or turn ClawCall into a bulk campaign tool.

Verify read-only, then place one controlled call

Start with account state. Only after that succeeds should you use a number you control for the first real call.

1 · Read-only verification

Check my ClawCall plan and remaining trial allowance. Do not place a call.

2 · Controlled connector test

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 the complete transcript afterward.

No manual selection required. When Microsoft Copilot is operating through a compatible MCP host, ask normally. The host can select ClawCall automatically when the task needs a call. Manual selection is optional and remains useful for diagnosis.
No fabricated artifact. This host was researched from official documentation but not live-tested with ClawCall for this release, so the page does not show or imply a successful call outcome.

The 9 ClawCall tools

Read the transcript before declaring success. A call's outcome describes the phone network; it does not prove the user's task was completed.

ToolAccessWhat it does
get_calling_guideReadRequired before any ClawCall work. Read current workflow guidance and examples before placing calls.
get_balanceReadRead the signed-in account's plan and remaining trial allowance.
place_callWriteStart one real outbound phone call and return immediately.
place_call_and_waitWriteStart one call and wait up to 90 seconds for an initial result.
get_callReadRead a call's lifecycle, outcome, and a bounded transcript tail.
get_call_transcriptReadRead the complete transcript for a call.
list_callsReadRead recent call history for the connected account.
get_recordingReadGet a temporary, playable recording URL when one is available.
hangup_callWriteStop a queued or live phone call.

Troubleshooting

The server returns 404 or no tools appear

Confirm the server URL is exactly https://api.clawcall.dev/mcp; the trailing /mcp is required. Refresh or reconnect after correcting it.

You see 401 or Sign in required

Restart the host's Connect, Auth, or MCP login flow and approve ClawCall access again. Do not replace OAuth with a pasted ClawCall API key.

The tool list looks stale

Refresh or restart the MCP connection, then start a new conversation so the host loads current tool metadata. The current server exposes nine tools.

A phone number is rejected

ClawCall currently calls real US numbers only. Use +1 E.164 format: +1 followed by ten digits.

The wait ended while the call is still running

Ask the host to poll get_call. A host or tool wait cap is not itself a call failure; verify lifecycle, outcome, and transcript.

A recording link no longer works

Recording URLs are temporary. Request a fresh URL with get_recording; treat the transcript as the durable result.

Disconnect and revoke access

01Disconnect or remove ClawCall in Microsoft Copilot.
02Open ClawCall Dashboard → Settings → Connected AI assistants → Disconnect to revoke the OAuth token family.

Microsoft Copilot and ClawCall FAQ

Do I need to choose ClawCall before every request?
No. Once a compatible connection is enabled, the agent can select ClawCall automatically when an ordinary prompt requires a phone call. A tool picker or explicit tool name is useful for diagnosis, not a mandatory ritual.
Why does ClawCall recommend Always allow or Allow all?
It lets the agent place the requested call, poll its status, and retrieve the transcript without repeated host approval prompts. This is ClawCall's recommended setting for the complete workflow; the connection remains limited to its granted OAuth scopes and the host's policy.
Does a successful network outcome prove the task succeeded?
No. A network outcome describes the call path. Read the full transcript 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 token family.

Sources, review method, and next steps

ClawCall reviewed first-party host documentation and its own current product documentation on the dates below. Only ChatGPT and Claude are labeled as live UI verified.

  1. Microsoft: Connect an agent to an existing MCP serverofficial-host-doc · checked
  2. GitHub: Extend Copilot Chat with MCP serversofficial-host-doc · checked
  3. Microsoft FY2026 Q4 earningsfirst-party-adoption · checked
  4. ClawCall: Hosted MCP for AI agentsfirst-party-product-doc · checked
  5. ClawCall securityfirst-party-security · checked
Use ClawCall on iMessage