First month free with promo codeFirst month free with codeEveryone else starts with 30 free calls and 30 minutes.Redeem DEEPGRAMStart free

Grok Build setup guide

Connect Grok Build to ClawCall with remote MCP

Add ClawCall with grok mcp add in the Grok Build CLI, then sign in when OAuth opens. Consumer Grok chat on X or grok.com is a different product.

Based on xAI’s documentation; not yet tested live with ClawCallUpdated

Remote MCP endpointhttps://api.clawcall.dev/mcp
Start freeSign in
Setup surface
Grok Build CLI
Transport
Remote HTTP MCP
Authentication
Automatic OAuth browser flow

Before you start

Availability. This guide covers Grok Build. Consumer Grok chat is a different product and does not offer this setup. You need a current Grok CLI, and project-level configuration can be managed separately from your user configuration.
  • A current Grok Build CLI.
  • 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 Grok Build to ClawCall

  1. Use Grok Build, not consumer Grok

    Open the Grok Build CLI. The consumer Grok chat product is not the setup surface documented by xAI for arbitrary MCP servers.

  2. Add ClawCall

    Register the remote HTTP server with the name clawcall.

    grok mcp add --transport http clawcall https://api.clawcall.dev/mcp

  3. Open the MCP manager

    Use Grok Build’s MCP manager to refresh the server. The documented manager can refresh configuration and start OAuth authentication.

  4. Complete OAuth

    On first use—or through the manager’s authenticate action—sign in to ClawCall and approve calls:read and calls:write.

  5. Review eleven tools

    Confirm the server is connected and all eleven tools are listed, including get_calling_guide.

  6. Always allow ClawCall

    Choose Always allow for all ClawCall tools when Grok Build shows approval controls. Keep credentials in your user store, not a repository.

OAuth scopes and host permissions

Grok Build 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 all tools

Set every ClawCall tool to Always allow so Grok Build can run the complete calling workflow without repeated prompts.

Always allow only skips the repeated approval prompts. It does not widen the two OAuth scopes, override project 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.

1. Read-only check

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

2. One controlled 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.

Ask normally. Grok Build can pick ClawCall automatically when a task needs a phone call; naming the tool is optional.

Tools and troubleshooting

ClawCall gives Grok Build 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

  1. Disconnect or remove ClawCall in Grok Build.
  2. 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 Grok Build’s own documentation and ClawCall’s product documentation, checked on the dates below.

  1. xAI: MCP servers in Grok BuildOfficial host documentation · checked
  2. Andreessen Horowitz: Top 100 Gen AI Consumer Apps, 6th editionIndependent market analysis · checked
  3. ClawCall: Hosted MCP for AI agentsClawCall documentation · checked
  4. ClawCall securityClawCall security · checked

Related pages

Can Grok Build make phone calls?Grok Bot setup guideOpenAI Codex setup guideHow to give your AI agent a phone numberAll 12 setup guidesFor AI agentsAI phone call APIAI phone calls with ClawCallAPI docsSecurity

Give Grok Build 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.

Start freeAll setup guides
Text ClawCall