Smitline
Related Servers
Alternatives to Smitline
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenancePhone, SMS & email for AI agents. One remote MCP server (Streamable HTTP, OAuth or API-key auth, no local install) exposing call, sms, email, and event tools; also usable via CLI, Python SDK, and OpenAPI. Self-hostable, AGPLv3.29AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to initiate and control outbound telephone calls and answer inbound calls through Telnyx and LiveKit, with realtime voice conversations powered by Gemini Live or OpenAI Realtime.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to speak and listen in real-time with interruption handling, using local ML models and hot-swappable adapters.37 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to place real phone calls, navigate IVR trees, and retrieve structured answers with transcripts and recordings.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to place phone calls for reservations, appointments, confirmations, and inquiries through a self-hosted MCP server, with language support and learning capabilities.68 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to place real phone calls, engage in spoken conversations across 12 languages, and report the outcomes for tasks like booking appointments, answering questions, negotiating, or confirming orders.MIT
TDQS
Scored across 13 tools
Most tools have clearly distinct purposes, and descriptions explicitly cross-reference alternatives (e.g., get_call vs wait_for_call vs list_calls, check_call_brief vs start_call). There is mild surface overlap between the call-retrieval tools and between check_call_brief and start_call, but the descriptions resolve it clearly.
All names use consistent snake_case verb_noun/verb_object form (save_call_note, end_call, get_profile, start_call, list_calls, send_call_instruction, transfer_call_to_me). No mixed conventions or vague verbs.
13 tools sit comfortably in the ideal range and each earns its place, covering the call lifecycle plus profile, contacts, and voice selection without redundancy.
The surface covers the full call lifecycle (brief check, start, wait, get, list, end, in-call instruction, transfer, post-call notes) plus profile read/update and voice listing. Minor gap: contacts are read-only (list_contacts) with no direct add/remove, though profile management partially compensates.