Google Gemini phone-call integration guide
How to connect ClawCall to Google Gemini
In the Gemini web app, open Connected Apps, add a custom app, and enter https://api.clawcall.dev/mcp. ClawCall supports Dynamic Client Registration, so advanced static credentials are unnecessary. Sign in and review the scopes. The connection works in Gemini Spark where the feature is available; normal Gemini chat without Spark custom apps is not the same setup surface.
Setup is based on the cited first-party host documentation; exact ClawCall compatibility is not claimed as live-tested.
https://api.clawcall.dev/mcpBefore you start
Gemini is included because independent cross-platform market analysis places it immediately behind ChatGPT on both web and mobile, while Gemini Spark now exposes a documented custom MCP URL path with OAuth registration.
- A Google Gemini account or workspace where Gemini Spark custom Connected App 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 Google Gemini 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.
Confirm Gemini Spark eligibility
Use a personal account and confirm the custom-app feature is available for your country, language, age, and account. Managed workspaces can expose different controls.
Open Connected Apps
In the Gemini web app, open Connected Apps settings and choose the control to add a custom app.
Enter the ClawCall MCP URL
Name the app ClawCall and enter https://api.clawcall.dev/mcp. The endpoint already follows the remote MCP contract Google requests.
https://api.clawcall.dev/mcpKeep dynamic registration
Do not open Advanced features to invent a client ID or secret. Google says those fields are for servers without Dynamic Client Registration; ClawCall supports DCR and OAuth discovery.
Sign in and approve scopes
Complete ClawCall sign-in, review calls:read and calls:write, and approve only if you trust the account and task.
Verify read-only first
Ask Gemini Spark to check your ClawCall plan without placing a call. Confirm get_balance succeeds and all nine tools are visible.
Place a controlled call
Use a number you control, keep Google's required write confirmation enabled, and ask for the full transcript after the call finalizes.
Gemini CLI alternative (official docs reviewed)
Gemini CLI supports Streamable HTTP, automatic OAuth discovery, and Dynamic Client Registration. Add ClawCall under mcpServers with httpUrl, then run /mcp auth clawcall. Setting trust to true is Gemini CLI’s server-level equivalent of always allowing tool calls; use it only after reviewing all nine tools.
{"mcpServers":{"clawcall":{"httpUrl":"https://api.clawcall.dev/mcp","trust":true}}}
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:readRead plan and trial state, call status, transcripts, history, and temporary recording access.
calls:writePlace and hang up real phone calls when you ask the assistant to do so.
Official ClawCall recommendation: Always allow all actions when Gemini offers it
ClawCall's official recommendation is Always allow or Allow all for every trusted agent connection. Gemini Spark currently documents mandatory manual confirmation for write actions, so follow that host restriction until Google exposes an equivalent trusted-server setting; never weaken it through an unsupported workaround.
Custom Gemini apps operate outside Google's control. A write approval can start a real call. Review the destination, task, and decision boundaries every time the host requires confirmation.
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.
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 the complete transcript afterward.
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.
| 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. |
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 a bounded transcript tail. |
get_call_transcript | Read | Read the complete transcript 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; 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
Google Gemini 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 a trusted agent place the requested call, poll its status, and retrieve the transcript without repeated host approval prompts. This is an elevated-risk choice because real calls can affect people and consume plan allowance.
- 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.
- Google: Connect a custom app to Gemini Spark with MCPofficial-host-doc · checked
- Google: Gemini CLI MCP serversofficial-host-doc · checked
- Andreessen Horowitz: Top 100 Gen AI Consumer Apps, 6th editionindependent-market-analysis · checked
- ClawCall: Hosted MCP for AI agentsfirst-party-product-doc · checked
- ClawCall securityfirst-party-security · checked