KaiCalls
Server Details
AI phone secretary: place calls, read transcripts, list calls, agents, and stats.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- cgallic/kaicalls-mcp
- GitHub Stars
- 0
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/5 across 21 of 21 tools scored. Lowest: 3.1/5.
Most tools have distinct purposes (calls, leads, agents, messaging, analytics). Overlap exists between update_agent_config and configure_agent_business_rules, but descriptions clarify the latter is for specific operational rules. The meta-tool request_kaicalls_update defers to other tools for common operations, reducing ambiguity.
Tools consistently use verb_noun pattern (get_, list_, configure_, send_, etc.) except for 'request_kaicalls_update' which mixes the server name and a less common verb. 'make_call' is slightly different but acceptable. Overall pattern is predictable.
With 21 tools, the server covers a broad domain (telephony, leads, agents, messaging, analytics, configuration) without feeling bloated. Each tool serves a specific need and the count is well-scoped for the apparent purpose.
The tool surface covers core operations (create, read, list) for calls, leads, and agents, but lacks update/delete for calls and leads (though request_kaicalls_update may fill some gaps). Missing campaign management beyond listing, and no call disposition tools. Notable but not severe gaps.
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!