Phonic

io.github.Phonic-CoPublished by GitHub account Phonic-Cov1.0.0Updated Nov 4, 2026

Create and manage voice agents, discover voices, review conversations, and search Phonic docs.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationMedia & Design

Overview

AI-generated overview

Phonic's remote MCP server lets an assistant build and manage voice agents, find voices, review conversations, and search Phonic documentation.

What you can do
  • Create and manage voice agents
  • Discover and browse available voices
  • Review past conversations
  • Search Phonic documentation
When to use it
Useful when you work with Phonic voice agents and want an assistant to set them up, pick voices, check how calls went, or look up Phonic docs without leaving the chat.
Requirements
A remote MCP endpoint at mcp.phonic.ai over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared, and a Phonic account is implied by the OAuth flow.
Before you install
OAuth grants the assistant access to your Phonic account, so agent creation and changes affect live voice agents. Reviewing conversations may expose customer call data to the assistant; grant only the access you need.

Installation

In SourceWeft

  1. Open Phonic in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Phonic-Co%2Fphonic/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "phonic": {
      "type": "http",
      "url": "https://mcp.phonic.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.0LatestNov 4, 2026
  2. v0.2.0Oct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.