Skip to main content
Glama
theYahia

mango-office-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mango-office-mcp

No user-submitted related servers found.

    Related Servers

    • @theyahia/mts-exolve-mcp

      theYahia
      A
      license
      B
      quality
      F
      maintenance
      Enables sending SMS, making calls, retrieving call recordings, managing phone numbers, and sending Viber messages through the MTS Exolve API.
      8
      53 npm
      MIT

    • rtk-vats

      sergey-akhmineev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage Rostelecom Virtual PBX telephony, including contacts, subscribers, call groups, call history, call recordings, numbers and routing, balance, and transparent proxy to any of ~240 endpoints.
      MIT

    • ringcentral-mcp

      MSPbotsAI
      A
      license
      A
      quality
      C
      maintenance
      Enables interaction with RingCentral phone system data, including account info, extensions, presence, call queues, contacts, and call logs/recordings, through MCP tools.
      13
      Apache 2.0

    • Planfix MCP Server

      popstas
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables integration with Planfix CRM and task management system, allowing lead management, contact/company management, task creation/search/commenting, and report generation via the Planfix REST API v2.0.
      65 npm
      11
      MIT

    • Kontur.Elba MCP

      apo100l
      A
      license
      A
      quality
      B
      maintenance
      Enables managing Kontur.Elba data through the official Public API, including organizations, bank accounts, counterparties, products, documents, invoices, and public links via MCP tools.
      4
      13 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 8 tools

    Disambiguation2/5

    There is clear overlap between get_calls and skill_call_history (both provide call logs, with the latter being today-only), and similarly get_stats vs skill_stats. While descriptions clarify the difference, agents could easily misselect when they want period-based vs today's data. Other tools like make_call, send_sms, get_users, get_recording are distinct.

    Naming Consistency2/5

    Naming is inconsistent: most tools use verb_noun (get_calls, make_call, send_sms), but two use the prefix 'skill_' (skill_call_history, skill_stats) which breaks the pattern. The 'skill_' prefix is unusual and suggests a different convention without clear rationale, making it harder to predict tool names.

    Tool Count4/5

    With 8 tools, the count is appropriate for a telephony server. However, the two redundant pairs (get_calls/skill_call_history, get_stats/skill_stats) could be consolidated, suggesting the surface is slightly padded but still reasonable.

    Completeness4/5

    The tools cover core telephony operations: retrieving calls, users, statistics, recordings, initiating calls, and sending SMS. Minor gaps exist (e.g., no call status updates, no user management beyond listing), but the main workflows are supported and no dead ends are evident.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources