ThunderPhone

io.github.thunderphonePublished by GitHub account thunderphonev1.1.0Updated Oct 24, 2026

Build, test, deploy and run AI phone agents: agents, numbers, calls, tests, knowledge, campaigns.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationAI & ML

Overview

AI-generated overview

ThunderPhone lets an assistant build, test, deploy and run AI phone agents, covering agents, numbers, calls, tests, knowledge and campaigns.

What you can do
Manage AI phone agents, including building, testing, deploying and running them, along with their phone numbers and campaigns. Work with calls and call tests. Manage knowledge used by the agents. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Use it when you want an assistant to help set up, test or operate AI phone agents and their numbers, calls, tests, knowledge or campaigns from a chat session.
Requirements
A remote endpoint at api.thunderphone.com or the local npm package @thunderphone/mcp over stdio. Authentication is required via OAuth; the Authorization header takes a bearer organization API key, or the THUNDERPHONE_API_KEY environment variable. The API key is optional if you have signed in with the thunderphone login command.
Before you install
It handles telephony and calling, so actions may place or manage real calls and campaigns, which can incur costs. The organization API key (THUNDERPHONE_API_KEY or the Authorization bearer token) is a secret; keep it out of shared logs and configs. Calls and campaign data may be sent to ThunderPhone's servers.

Installation

In SourceWeft

  1. Open ThunderPhone 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.thunderphone%2Fthunderphone/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": {
    "thunderphone": {
      "type": "http",
      "url": "https://api.thunderphone.com/v1/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.1.0LatestSep 20, 2026
  2. v1.0.0Sep 17, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.