Skip to main content
Glama
smallest-inc

Smallest MCP Server

Official
by smallest-inc

Related Servers

Alternatives to Smallest MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An 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
    • A
      license
      B
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with the VoIPbin CPaaS platform, exposing tools for managing calls, flows, messaging, conferencing, and more.
      52
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP 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 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 84 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues