Bubblyphone Agents

Created By
BubblyPhone2 months ago
MCP server for BubblyPhone — make AI phone calls, manage phone numbers, configure voice agents, and track billing from any AI assistant. Supports Claude, ChatGPT, Cursor, and any MCP-compatible client.
Overview

BubblyPhone Agents MCP Server

Turn any AI assistant into a phone agent. BubblyPhone's MCP server lets you make real phone calls powered by AI — book reservations, schedule appointments, set up customer support lines, or have your AI agent call anyone on your behalf.

Features

  • Make AI phone calls — Initiate outbound calls with AI agents that handle the conversation
  • Manage phone numbers — Search, purchase, and configure numbers in 30+ countries
  • Configure AI agents — Set system prompts, choose AI models (Gemini, GPT), select voices
  • Monitor calls — View call events, transcripts, and recordings
  • Track billing — Check balance, usage, and transaction history
  • Mid-call control — Inject context, transfer calls, or hang up

Quick Start

Add to your Claude Desktop or Cursor config:

{
  "mcpServers": {
    "bubblyphone": {
      "command": "npx",
      "args": ["@bubblyphone/mcp-server"],
      "env": {
        "BUBBLYPHONE_API_KEY": "bp_live_sk_your_key_here"
      }
    }
  }
}
Get your API key at https://agents.bubblyphone.com

Server Config

{
  "mcpServers": {
    "bubblyphone": {
      "command": "npx",
      "args": [
        "@bubblyphone/mcp-server"
      ],
      "env": {
        "BUBBLYPHONE_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
BubblyPhone
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago