KaiCalls
Server Details
AI phone secretary: place calls, read transcripts, list calls, agents, and stats.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- KaiCalls/kaicalls-mcp
- GitHub Stars
- 0
- Server Listing
- KaiCalls MCP Server
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 44 of 51 tools scored. Lowest: 3.3/5.
Tools have distinct purposes overall, but there is overlap (e.g., update_agent_config vs configure_agent_business_rules vs request_kaicalls_update) and several tools handle similar concepts (e.g., get_balance vs list_overage_charges). Descriptions are detailed and help, but the sheer number forces agents to carefully parse intent.
Most tools follow a consistent verb_noun pattern (e.g., create_agent, list_agents, send_sms). Minor deviations include longer multi-word names (configure_agent_business_rules) and a single outlier (request_kaicalls_update), but overall the pattern is predictable.
51 tools is excessive for an MCP server. While the domain is broad, this many tools overloads the agent's selection space, making it hard to pick the right one. A more focused split into multiple servers would improve usability.
The tool set covers many aspects (numbers, agents, calls, SMS, leads, webhooks, billing, etc.), but notable gaps exist: no get_agent, no delete_agent, no update or delete campaign, and no delete lead. These missing operations may cause agent failures in common workflows.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityBmaintenanceManage voice AI agents, make calls, run campaigns, and control phone numbers through natural language.58201MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to place real phone calls, navigate IVR trees, and retrieve structured answers with transcripts and recordings.MIT

selectic-mcpofficial
AlicenseNot gradedqualityAmaintenanceEnables AI assistants to call, text, and email businesses on your behalf, read back transcripts, recordings, and replies.42MIT- FlicenseBqualityDmaintenanceEnables interaction with Retell AI's voice and chat agent platform. Build, deploy, and manage AI phone agents, configure conversation flows, handle calls/chats, and manage phone numbers through natural language.52
Your Connectors
Sign in to create a connector for this server.