Labsco
MCP SERVER

Magpipe

by elagerway ↗

Run a Magpipe voice-and-SMS stack from your coding tool — build agents, buy numbers, place calls, read transcripts and manage knowledge sources without opening the dashboard.

Telephony, SMS & Voice Agents
Summary
The whole account, including the parts that spend money.

This is not a reporting connector — the same key that lists your calls can provision a phone number, dial out, and rotate your API keys through `manage_api_keys`. That breadth is what makes it useful for building an agent end to end from an editor, and it is also the reason to think about which key you paste into the config.

What it is

The MCP server for Magpipe, a platform for AI phone agents. It puts the whole account behind tool calls: the agents themselves, the phone numbers they answer on, the calls and SMS they exchange, the contacts they talk to, and the knowledge they draw on.

What you get
  • Agent lifecycle — `list_agents`, `get_agent` for full detail including assigned numbers and custom functions, `create_agent`, `update_agent`, `delete_agent`
  • Calls — `list_calls`, `get_call` for details with transcript and summary, `initiate_call` to dial out, `terminate_call` to hang up a live call, `get_recording` for a signed URL
  • Messaging — `list_messages`, `get_message`, `send_sms`
  • Phone numbers — `search_phone_numbers` for what is available, `provision_phone_number` to buy one, `list_phone_numbers`, `release_phone_number`
  • Contacts — `list_contacts`, `get_contact`, `create_contact`, `update_contact`, `delete_contact`
  • Knowledge base — `list_knowledge_sources`, `add_knowledge_source` for a URL, `add_knowledge_manual` for pasted text, `sync_knowledge_source` to re-crawl, `delete_knowledge_source`
  • Booking — `get_calendar_slots`, `create_booking`, `cancel_booking`
  • The rest of the account — `list_voices` and `delete_voice`, `list_models`, `chat_with_agent`, `list_chat_sessions`, `list_custom_functions`, `create_custom_function`, `manage_dynamic_variables`, `list_scheduled_actions`, and `manage_api_keys`
Requirements

A Magpipe account and an API key starting with `mgp_`, generated at magpipe.ai/settings under the API tab. Pass it as `MAGPIPE_API_KEY` in the client's env block and run the server with `npx -y magpipe-mcp-server`; `MAGPIPE_API_URL` overrides the base URL, which otherwise points at `https://api.magpipe.ai/functions/v1`. Package `magpipe-mcp-server` at 0.1.5, MIT.

Setup effort

One command plus a key — npx -y magpipe-mcp-server, then supply credentials