placetel-web-api-mcp-server
Related Servers
Alternatives to placetel-web-api-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceMCP server for Voximplant API enabling calls, SMS, recordings, scenarios, and rules management with 11 tools and 2 skills.2344 npm3MIT
- FlicenseAqualityCmaintenanceAn MCP server that wraps the UTEL IP-telephony REST API as MCP tools, enabling LLM agents to make authenticated HTTP requests to the UTEL API via a simple tool interface.11-
- AlicenseNot gradedqualityFmaintenanceA single MCP server that provides a provider-neutral 14-tool contract for telephony operations (calls, SMS, recordings, transcripts, and number lifecycle), supporting hosted, fully local, or bring-your-own-key backends.1MIT
- AlicenseNot gradedqualityDmaintenanceA standalone MCP server for managing Zoom Phone telephony, providing 117 tools for auto receptionists, call queues, voicemail, devices, SMS, and more via the Zoom Phone REST API.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server wrapping the full VitoDeploy REST API to manage projects, servers, sites, databases, services, workers, SSL, DNS, and more through any MCP-compatible agent, with 108 tools covering every endpoint.MIT
- AlicenseAqualityAmaintenanceMCP server for Planfix API enabling task, project, contact, and comment management with 10 tools and 2 skills.2025 npm5MIT
TDQS
Scored across 124 tools
Most tools map to a clearly distinct resource and action, with names and endpoint hints that help separate similar areas like calls, call detail records, and call-center calls. A few CTI and routing tools (e.g. cti_dial_digit vs. cti_send_dtmf_digits, routing vs. routing_plan) could still be confused, so the set is mostly but not perfectly distinct.
Every tool uses the placetel_ prefix with snake_case verb_noun/resource naming, and CRUD operations are highly predictable. Minor variants such as add_subscription, upsert_provisioning_custom_configuration, and get_me are domain-specific but do not break the overall convention.
124 tools is far beyond the practical 3-15 range for an MCP toolset and creates very high context and selection overhead. Although the tools mirror many real API endpoints, the surface is too large to be well-scoped as an agent-facing tool set.
The surface covers a broad range of Placetel resources: calls, contacts, numbers, SIP users, routing, provisionings, faxes, recordings, users, Webex, and Microsoft Teams. Some resources lack full lifecycle operations (e.g. sites/devices/SIM cards are mostly list/get only, and call-center agents/queues lack delete/get), but core workflows are well covered.