Server facts
mcp-server
Project
- Author
- elagerway
- Website
- magpipe.ai
- License
- Not specified
- Category
- Communication
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- Not recordedPart of the elagerway/magpipe monorepo
- Last commit
- Data as of
Overview
Magpipe’s communications workflows can be managed from Claude Code or Cursor through this MCP integration. Developers can create and revise agents, inspect their settings, and manage the phone numbers, knowledge sources, custom functions, and extraction variables associated with them. Calling tools cover outbound dialing, ending active calls, and reviewing transcripts, summaries, and recordings. SMS tools support message retrieval and sending from service numbers, while contact tools provide search, filtering, and record maintenance. Phone number workflows include searching by location or type, purchasing numbers, assigning them to agents, and checking carrier information.
Agent preparation and evaluation extend beyond configuration. Knowledge can come from crawled URLs or manually supplied text, with options to refresh URL sources. Developers can browse voices and language models, exchange chat messages with an agent, and continue a conversation using its session identifier. Testing tools organize cases into suites, support scripted or silent callers, and check phrases, function use, and call duration. Results expose assertion outcomes and AI analysis. Other tools handle Cal.com availability and bookings, API key administration, and inspection of scheduled actions.
mcp-server setup notes
- mcp-server records stdio only; confirm a network transport upstream before planning remote access.
- mcp-server: Part of the elagerway/magpipe monorepo
- mcp-server has no recorded license; confirm reuse terms in its repository.