Skip to main content
Glama
Wagner-Emden-IT-Services

placetel-web-api-mcp-server

Related Servers

Alternatives to placetel-web-api-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      MCP server for Voximplant API enabling calls, SMS, recordings, scenarios, and rules management with 11 tools and 2 skills.
      23
      44 npm
      3
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      An 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.
      1
      1
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      A 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.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for Planfix API enabling task, project, contact, and comment management with 10 tools and 2 skills.
      20
      25 npm
      5
      MIT

    TDQS

    C2.7/5.0

    Scored across 124 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count1/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive