Grok Bot setup guide
Make phone calls from Grok Bot with ClawCall
Yes—Grok Bot can make real US phone calls once ClawCall is connected. Message your Bot “Get the ClawCall MCP so you can make phone calls for me,” approve the ClawCall sign-in, and it can call businesses for you and report what was said. You never paste an API key into chat.
https://api.clawcall.dev/mcp- Setup surface
- Ask your Bot in chat
- Transport
- Remote HTTPS MCP
- Authentication
- OAuth from the Bot’s connect card (via Cursor)
Before you start
- The Grok Bot app on desktop or iOS, with a plan that includes Grok Bot.
- A ClawCall account.
- A real US +1 destination for an English-language call, in 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 Bot to ClawCall
Ask your Bot for ClawCall
Open Grok Bot and message any Bot:
Get the ClawCall MCP so you can make phone calls for me.Grok Bot has no settings form for custom MCP servers. The Bot registers ClawCall’s remote server,
https://api.clawcall.dev/mcp, on your account, and every Bot you own can then use it. If it reaches for a different catalog plugin, sayAdd a custom MCP server called ClawCall at https://api.clawcall.dev/mcp.
One message is the whole install request. Select Authorize on the connect card
The Bot adds ClawCall and posts a connect card in the chat. Select Authorize.
The connect card appears right in the conversation. Continue to sign in
Grok Bot explains that you sign in to ClawCall directly and that it never sees your password. Select Continue to open ClawCall in your browser.
Grok Bot’s connect dialog before the browser sign-in. Allow the connection in ClawCall
Sign in to the ClawCall account the Bot should call from, review the
calls:readandcalls:writepermissions, and choose Allow connection.The page says Cursor wants to use ClawCall and shows an “Unverified AI client” notice with the destination. That is expected: Grok Bot runs its connectors through Cursor’s MCP backend. Continue only if the destination is exactly
https://www.cursor.com. If your browser then asks to open Grok Bot, allow it.
Grok Bot connects through Cursor, so the consent page names Cursor. Confirm ClawCall is added
Back in Grok Bot, the card changes to Added with 11 tools, and the Bot says ClawCall is ready for calls. New tools work from your next message.
ClawCall added with all eleven tools. Run the read-only check
Before any real call, ask:
Check my ClawCall plan and remaining trial allowance. Do not place a call.The Bot callsget_balanceand reports your plan without dialing anyone.
A read-only check proves the connection before the first call.
OAuth scopes and host permissions
The host discovers ClawCall’s authorization-server and protected-resource metadata, registers itself as a public client, and completes OAuth 2.1 authorization code with PKCE S256. It receives revocable tokens, never your ClawCall API key, and the consent flow requests two bounded scopes.
calls:read- Read plan/trial state, call settings, reserved-number status, call status, captured transcript evidence when present, history, and temporary recording access when available.
calls:write- Place and hang up real phone calls or update call settings when you ask the assistant to do so.
Recommended: Always allow ClawCall
If Grok Bot asks before a ClawCall action, choose the option that always allows ClawCall, or add an Auto Review allow instruction such as “Allow ClawCall phone calls I ask for.” The Bot can then place the call, poll its status, and read any transcript evidence captured without stopping at every step. In our test, the read-only check ran without an approval prompt.
Always allow only skips repeated approval prompts. It does not widen the two OAuth scopes, override your team’s Cursor MCP 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.
Real Grok Bot example: a no-answer, then a quoted rate
At 3 AM on a Sunday, we asked Grok Bot to call the Domino’s nearest Union Square for a carryout price. The store was closed, and the Bot reported that the call rang out with no answer instead of guessing a price. We then asked it to call the Hilton San Francisco Union Square front desk. The Bot worked through the phone menu, waited while the desk checked, and returned the quoted rate and taxes. It asked about price only; nothing was ordered or booked.
The 11 ClawCall tools
Read the transcript evidence actually captured before declaring success. A call’s outcome describes the phone network; it does not prove the task was completed.
| Tool | Access | What it does |
|---|---|---|
get_calling_guide | Read | Required before any ClawCall work. Read current workflow guidance and examples before placing calls. |
get_balance | Read | Read the signed-in account's plan and remaining trial allowance. |
get_call_settings | Read | Read reusable voice/personality, reserved-number capabilities, and inbound-assistant availability. |
update_call_settings | Write | Update global or inbound call settings in separate calls. |
place_call | Write | Start one real outbound phone call and return immediately. |
place_call_and_wait | Write | Start one call and wait up to 90 seconds for an initial result. |
get_call | Read | Read a call's lifecycle, outcome, and the latest transcript lines when present. |
get_call_transcript | Read | Read the transcript evidence captured for a call. |
list_calls | Read | Read recent call history for the connected account. |
get_recording | Read | Get a temporary, playable recording URL when one is available. |
hangup_call | Write | Stop 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, including the trailing/mcp. 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 eleven 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 time limit is not a call failure. Check the lifecycle, the outcome, and the transcript field, which can be empty. - A recording link no longer works
- Recording URLs are temporary.
get_recordingreturns the original link and cannot renew it after expiry. ClawCall deletes transcripts 7 days after a call ends and recordings 10 minutes after a call ends.
Disconnect and revoke access
- Disconnect or remove ClawCall in Grok Bot.
- Open ClawCall Dashboard → Settings → Connected AI assistants → Disconnect to revoke its OAuth tokens.
FAQ
- Can Grok Bot make phone calls?
- Not by itself. A Bot works on a cloud computer with a browser, files, and a terminal, but it has no phone line. With the ClawCall MCP connected, a Bot can call a real US +1 number, work through a phone menu, wait on hold, and return the transcript evidence captured on the call. Calls are in English.
- Is this the same as Grok Build or Grok on grok.com?
- No. Grok Bot adds MCP servers when you ask it in chat. Grok Build, the terminal coding agent, uses
grok mcp add, and Grok chat on grok.com has its own connector settings. Setup steps for one product do not carry over to the others. - Do my other Bots get ClawCall too?
- Yes. Plugins and MCP servers you add belong to your account, so every Bot you own can use ClawCall after one setup. On a Cursor team, your admin’s MCP policy still decides whether the server is allowed.
- Why does the ClawCall consent page say Cursor?
- Grok Bot runs its connectors through Cursor’s MCP backend, so the OAuth client that asks for access is Cursor and the authorization result goes to https://www.cursor.com. In ClawCall Dashboard → Settings → Connected AI assistants, the Grok Bot connection appears as Cursor. Disconnecting that row revokes only that connection.
- 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 custom 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.
Sources
Setup steps come from Grok Bot’s own documentation and ClawCall’s product documentation, checked on the dates below.
- xAI: Grok Bot documentation
- xAI: Introducing Grok Bot
- xAI: Grok Bot for teams and enterprises
- ClawCall: Hosted MCP for AI agents
- ClawCall security
Related pages
Give Grok Bot 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.