GET STARTED

MCP Server

The Model Context Protocol (MCP) is an open standard that allows AI assistants connect to external systems through a uniform interface. Phonic’s MCP server exposes the Phonic API as MCP tools, so a client such as Claude Code, Codex, or Cursor can manage your agents, conversations, voices, and projects.

This page covers Phonic’s inbound MCP server, where an MCP client connects to Phonic to drive the API. It is distinct from MCP Tools, the outbound feature where a Phonic agent connects to your external MCP servers to call their tools during a conversation.

Phonic’s MCP server stays up to date with the Phonic API — every endpoint is exposed as an MCP tool. See the API reference for the full list of resources and operations.

Setup

Phonic’s MCP server supports OAuth, so most clients just need the server URL and will prompt you to sign in through your browser. If your client or environment can’t complete a browser sign-in, use an API key instead.

Connect via OAuth

  1. Go to the connectors page.
  2. Click Add custom connector and enter https://mcp.phonic.ai/mcp.
  3. Click Connect and sign in when your browser opens.

Connect via API key

Create an API key on the API keys page and provide it to your client as a bearer token. Each request runs with that key’s permissions, exactly as a REST call would.

Your API key carries full access to your workspace. Store it as a secret and never commit it or expose it to a browser.

  1. Go to the connectors page.
  2. Click Add custom connector and enter https://mcp.phonic.ai/mcp.
  3. When prompted to authenticate, add an Authorization header set to Bearer YOUR_PHONIC_API_KEY.

Example prompts

Once connected, ask Phonic:

  • “Create an agent named support-bot and assign it a phone number.”
  • “List my last 10 conversations and summarize the ones flagged for follow-up.”
  • “Which voices are available, and what does the default agent use?”
  • “Add a webhook tool to support-bot that posts to my orders endpoint.”