A
licenseA
qualityD
maintenanceManage voice AI agents from Claude Code, Cursor, VS Code, or any MCP-compatible assistant.
3
03
MIT
Atoms MCP Server
by aryasmol
Related Servers
Alternatives to Atoms MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceManage voice AI agents, make calls, run campaigns, and control phone numbers through natural language.5813 npm1MIT
movoice-mcpofficial
AlicenseAqualityCmaintenanceCreate and manage voice AI agents using natural language from Claude Desktop or Cursor. Enables agent creation, listing, updating, deletion, and viewing call logs.73 npmMIT
Smallest MCP Serverofficial
AlicenseAqualityAmaintenanceMCP server for the Smallest AI platform that enables managing AI voice agents, debugging calls, and viewing analytics directly from your IDE.8417 npm1MIT- AlicenseNot gradedqualityDmaintenanceControl your Famulor AI voice agents — calls, leads, campaigns, knowledge bases, conversations, WhatsApp, SIP trunks — directly from Claude, Cursor, Windsurf, VS Code and any other MCP-compatible client.37 npm1MIT
- AlicenseNot gradedqualityFmaintenanceConnects AI coding assistants to the Jules API for autonomous coding sessions. Enables creating and managing coding sessions, GitHub integration, plan approval workflows, and real-time activity tracking directly from your IDE.3 npm6MIT
TDQS
A3.9/5.0
Scored across 11 tools
Disambiguation5/5
Each tool maps to a distinct resource or action—agent CRUD, call logs, aggregate usage, single-call debugging, campaigns, phone numbers, and outbound calls. The call-related tools are clearly separated by scope (list vs. aggregate vs. single-call deep-dive), so an agent can reliably select the right one.
Naming Consistency5/5
All names follow a consistent snake_case verb_noun pattern: get_* for read operations, create_/update_/delete_ for agent mutations, and make_call/debug_call for actions. There are no mixed conventions or vague verbs.
Tool Count5/5
11 tools is well-scoped for an AI-calling platform: enough to cover meaningful agent and call workflows without redundancy. The set feels deliberately chosen rather than bloated or thin.
Completeness4/5
Agent lifecycle is fully covered with create, list, config update, prompt update, and delete, and call workflows are covered via make_call, get_call_logs, debug_call, and get_usage_stats. Campaigns and phone numbers are read-only, and there is no singular get_agent by ID, but these are minor gaps that agents can typically work around.
Maintenance
ActivityInactive
ResponsivenessNo issues