Smallest MCP Server
OfficialRelated Servers
Alternatives to Smallest MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceMCP server for Vapi.ai that enables AI coding assistants to manage voice assistants, make outbound calls, and access call history directly from their development environment.164 npm2MIT
- FlicenseCqualityDmaintenanceMCP server enabling interaction with Telnyx telephony, messaging, and AI assistant APIs through natural language.46-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents hands to make phone calls, send messages, and handle CRM/task workflows. It runs with a simulated provider for zero-cost testing and can switch to real providers like Twilio and ElevenLabs.MIT

VoIPbin MCP Serverofficial
AlicenseBqualityCmaintenanceAn MCP server that enables AI assistants to interact with the VoIPbin CPaaS platform, exposing tools for managing calls, flows, messaging, conferencing, and more.521MIT- AlicenseAqualityDmaintenanceMCP server for BubblyPhone that lets AI assistants make real phone calls, manage AI voice agents, buy phone numbers in 30+ countries, and track billing. Supports 20 tools for full telephony control.202 npm1MIT

Chamade MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceMCP server for Chamade — a voice and chat gateway that lets your AI agent join meetings and DMs on Discord, Microsoft Teams, Google Meet, Telegram, SIP, Zoom, Nextcloud Talk, Slack, and WhatsApp.70 npmMIT
TDQS
Scored across 84 tools
Most tools are clearly separated by resource (agents, playbooks, campaigns, audiences, billing, webhooks, analytics), but there is notable overlap in the analytics cluster: get_usage_stats, get_duration_stats, get_latency_summary, get_dashboard, get_call_volume, get_call_outcomes, get_agent_performance, get_hourly_performance, get_pickup_rates, get_phone_number_trends, get_weekly_trends, get_attempt_cohorts, get_call_counts_by_day, get_credit_usage, get_call_start_distribution, and get_daily_summary all return usage/performance metrics with subtly different slices. An agent could easily pick the wrong analytics tool. The playbook/branch/draft/revision cluster (update_playbook, add_playbooks, configure_playbooks, get_playbooks, list_branches, create_branch, get_branch_draft, publish_draft, list_revisions, get_revision, diff) is also dense and requires careful reading to distinguish.
The dominant pattern is verb_noun (get_agents, create_agent, update_agent, delete_agent, list_calls, make_call, publish_draft, redeem_coupon), which is consistent and predictable. Minor deviations exist: 'diff' is a bare verb with no noun, and 'chat_with_agent' uses a prepositional phrase rather than a simple verb_noun form. Overall the naming is highly readable and follows a clear convention.
84 tools is far beyond the typical well-scoped MCP server range. While the server covers many domains (agents, playbooks, campaigns, audiences, calls, billing, webhooks, analytics, TTS/STT), the sheer count creates a heavy surface that is difficult for an agent to navigate. The analytics section alone has 16+ tools that could be consolidated. This feels like a full REST API dump rather than a curated MCP tool set.
The tool surface is remarkably comprehensive: full CRUD for agents, playbooks, campaigns, audiences, webhooks, and branches; call lifecycle (make_call, debug_call, list_calls, export_campaign_logs); billing and credit management; and extensive analytics. Minor gaps exist — there is no update_campaign or update_audience tool, and no way to unarchive an agent — but these are workarounds (delete/recreate, or use the web app). For the stated purpose of managing the Smallest AI platform, coverage is strong.