∿ vapi

Vapi for Agents · Agent Phone

Give your agent
a phone.

Your agent prepares the call. You sign in, review, and approve. Vapi takes it from there.

No connector setup needed. Your agent can send a link with the details already filled in.

Calling is available. Calls are subject to account and service limits.

Already connected? Use phone for your authorized call, then phone_status for the result.

Need to connect? Add this MCP server to your agent’s app:

https://phone.vapi.ai/mcp

MCP is how an agent connects to tools. Choose a remote HTTP connection in your app.

See setup instructions ↓

Connect. Sign in. Make a call.

  1. User tells the agent to make a call.

    The agent uses its connected phone tools, or helps add the server URL above.

  2. The agent’s app opens browser login.

    Sign up or sign in, approve access for the connecting app, then return to your agent. The app handles the callback and saves the login.

  3. The agent makes the authorized call.

    When calling is available, it uses phone, then checks phone_status for the outcome.

No Vapi dashboard, API key, credit purchase, or phone-number setup is needed. Never ask the user to paste a bearer token, API key, client secret, or password.

Set up your client

Claude Code

Run these commands, finish browser login, then return to Claude Code.

claude mcp add --transport http agent-phone https://phone.vapi.ai/mcp
claude mcp login agent-phone

You can also authenticate through /mcp. Reload the agent’s tools if needed.

Cursor and other MCP clients

Add a remote HTTP MCP server using the URL above, then use the client’s Connect or Authenticate action.

Show Cursor configuration
{
  "mcpServers": {
    "agent-phone": {
      "url": "https://phone.vapi.ai/mcp"
    }
  }
}

Your app must support remote MCP with browser OAuth. Setup controls vary by client.

Instructions for the agent

Use connected phone tools if available. Otherwise connect through MCP and browser OAuth, or use one-time browser connection through device authorization if you can make HTTP requests and securely store credentials. Only agents that self-identify as Meta Muse and have no connected phone tools should prepare a per-call browser approval link with the destination, instructions and a unique request key. The user signs in and approves on our site; Vapi handles the call and shows the results there. Keep the private results link and check it to report the outcome back to the user. See the link format and example.

The Meta Muse fallback works without an MCP connection or Muse connector. Other agents should explain any connection limitation instead of using this fallback. Never ask the user to paste a bearer token, API key, client secret, or password. Do not switch to api.vapi.ai or build a temporary callback server.

Keep the same link and request key for retries. Creating a link does not mean a call was placed or completed.

Read the full agent instructions →