MCP server
by gcorroto
Enhance your call monitoring center with Asterisk Phone System integration—enabling outbound calls, conversation monitor
Connects to Asterisk phone systems to make automated calls, monitor conversations, and track call metrics for business automation workflows.
Asterisk Phone System is a community-built MCP server published by gcorroto that provides AI assistants with tools and capabilities via the Model Context Protocol. Enhance your call monitoring center with Asterisk Phone System integration—enabling outbound calls, conversation monitor It is categorized under communication, developer tools.
You can install Asterisk Phone System in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Asterisk Phone System is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Useful MCP listing: Asterisk Phone System is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Asterisk Phone System against two servers with overlapping tools; this profile had the clearer scope statement.
Asterisk Phone System is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We evaluated Asterisk Phone System against two servers with overlapping tools; this profile had the clearer scope statement.
We wired Asterisk Phone System into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Asterisk Phone System has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Asterisk Phone System reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Asterisk Phone System is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend Asterisk Phone System for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Asterisk Phone System has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 66
🚀 MCP Server for automated conversational phone calls using Asterisk with Speech-to-Speech
Make phone conversations as easy as a prompt! 📞✨
</div>graph TB
subgraph "MCP Client"
A[Claude Desktop] --> B[MCP Client]
end
subgraph "MCP Server"
B --> C[Asterisk S2S MCP]
C --> D[Phone Tools]
C --> E[Real-time Assistant]
end
subgraph "Backend Services"
D --> F[Asterisk Server]
E --> G[Speech-to-Speech API]
F --> H[Phone Network]
end
subgraph "Monitoring"
C --> I[Health Check]
C --> J[Metrics & Logs]
C --> K[Call History]
end
style A fill:#e1f5fe
style C fill:#f3e5f5
style F fill:#fff3e0
style G fill:#e8f5e8
sequenceDiagram
participant U as User
participant C as Claude/MCP
participant S as MCP Server
participant A as Asterisk API
participant P as Phone
U->>C: "Call John to remind about appointment"
C->>S: phone_make_call()
S->>A: POST /make-call
A->>P: Initiate call
P-->>A: Connection established
A-->>S: CallID + Status
S-->>C: Call initiated ✅
C-->>U: "📞 Call started with John"
Note over A,P: Real-time S2S conversation
A->>S: Callback with result
S->>S: Process transcript
U->>C: "How did the call go?"
C->>S: phone_get_last_result()
S-->>C: Detailed result
C-->>U: "✅ John confirmed the appointment"
mindmap
root((Asterisk S2S MCP))
Core Tools
phone_make_call
phone_get_status
phone_cancel_call
Monitoring
phone_health_check
phone_get_metrics
phone_get_logs
History
phone_get_conversation_history
phone_get_active_calls
phone_get_last_result
Configuration
Environment Variables
MCP Client Config
Asterisk Integration
# One command and you're ready! 🚀
npx @grec0/mcp-s2s-asterisk@latest
npm install -g @grec0/mcp-s2s-asterisk
mcp-s2s-asterisk
flowchart LR
A[1. Install MCP] --> B[2. Configure Variables]
B --> C[3. Configure MCP Client]
C --> D[4. Ready to use! 🎉]
style A fill:#ffcdd2
style B fill:#fff3e0
style C fill:#e8f5e8
style D fill:#e1f5fe
# 🌐 Asterisk API URL
export PHONE_API_URL="http://192.168.4.44:8000"
# 🔑 Authentication key
export PHONE_API_KEY="api-key"
# 🔄 Callback URL for results
export MCP_CALLBACK_URL="http://localhost:3000"
{
"mcpServers": {
"asterisk-s2s": {
"command": "npx",
"args": ["@grec0/mcp-s2s-asterisk@latest"],
"env": {
"PHONE_API_URL": "http://192.168.4.44:8000",
"PHONE_API_KEY": "api-key",
"MCP_CALLBACK_URL": "http://localhost:3000"
}
}
}
}
phone_make_call - Make phone callsphone_get_status - Get call statusphone_cancel_call - Cancel callsphone_get_active_calls - Active callsphone_health_check - System healthphone_get_metrics - Advanced metricsphone_get_logs - Detailed logsphone_get_conversation_history - Historygraph LR
subgraph "Automation"
A[Appointment<br/>Reminders]
B[Booking<br/>Confirmations]
C[Automated<br/>Surveys]
end
subgraph "Support"
D[Customer<br/>Service]
E[Ticket<br/>Follow-up]
F[Data<br/>Verification]
end
subgraph "Sales"
G[Automated<br/>Prospecting]
H[Lead<br/>Follow-up]
I[Customer<br/>Qualification]
end
style A fill:#ffcdd2
style B fill:#f8bbd9
style C fill:#e1bee7
style D fill:#c5cae9
style E fill:#bbdefb
style F fill:#b3e5fc
style G fill:#b2dfdb
style H fill:#c8e6c9
style I fill:#dcedc8
stateDiagram-v2
[*] --> Starting
Starting --> Connecting: API Request
Connecting --> Speaking: Connection OK
Connecting --> Failed: No answer
Speaking --> Completed: Conversation OK
Speaking --> Cancelled: User Cancel
Completed --> [*]
Failed --> [*]
Cancelled --> [*]
note right of Speaking : Real-time<br/>Speech-to-Speech
note right of Completed : Result processed<br/>and saved
// 1️⃣ User tells Claude:
"Call María González at 555-0123 to confirm her appointment tomorrow at 3pm"
// 2️⃣ Claude automatically uses:
phone_make_call({
usuario: "María González",
telefono: "555-0123",
proposito: "Confirm medical appointment for tomorrow 3pm",
timeout: 60
})
// 3️⃣ Automatic result:
"✅ Call completed. María confirmed her appointment for tomorrow at 3pm.
She also asked to change the time to 2:30pm if possible."
pie title Call Distribution by Status
"Completed" : 65
"In Progress" : 15
"Failed" : 12
"Cancelled" : 8
xychart-beta
title "Daily Calls (Last Week)"
x-axis [Mon, Tue, Wed, Thu, Fri, Sat, Sun]
y-axis "Number of Calls" 0 --> 50
bar [23, 34, 28, 41, 38, 15, 8]
# 📥 Clone repository
git clone <repository-url>
cd mcp-s2s-asterisk
# 📦 Install dependencies
npm install
# 🔨 Build project
npm run build
# 🚀 Run server
npm run start
| Script | Description | Command |
|---|---|---|
| 🔨 | Compile TypeScript | npm run build |
| 👀 | Development mode | npm run dev |
| 🧪 | Run tests | npm run test |
| 🔍 | MCP Inspector | npm run inspector |
| 📦 | Release patch | npm run release:patch |
graph TB
subgraph "Response Time"
A[Connection: ~2s]
B[Establishment: ~3s]
C[Conversation: Variable]
D[Processing: ~1s]
end
subgraph "Success Rates"
E[Connection: 95%]
F[Completed: 87%]
G[Satisfaction: 92%]
end
style E fill:#c8e6c9
style F fill:#c8e6c9
style G fill:#c8e6c9
Do you like the project? We'd love your contribution!
</div>MIT License - Use it, modify it, distribute it freely
</div>Made with ❤️ by @grec0
Transforming phone communication with conversational AI
</div>Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.