Skip to main content
Glama
EfrainTorres

armavita-quo-mcp

by EfrainTorres
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to armavita-quo-mcp

No user-submitted related servers found.

    Related Servers

    • orbit-mcp

      Devotel
      A
      license
      Not graded
      quality
      C
      maintenance
      A stdio-based MCP server that exposes the Orbit CPaaS API as tools, enabling sending SMS, managing campaigns, and other communication workflows through natural language in MCP clients.
      6 npm
      MIT

    • @nightsquawktech/gohighlevel

      NightSquawk
      A
      license
      A
      quality
      B
      maintenance
      Stdio MCP server for curated GoHighLevel API v2 coverage, enabling create, update, and delete operations on custom fields, contacts, opportunities, tags, conversations, calendars, and more, with safe guarded destructive tools requiring explicit confirmation.
      56
      28 npm
      2
      AGPL 3.0

    • Personal OS MCP

      likalg
      F
      license
      A
      quality
      B
      maintenance
      MCP server for Personal OS API that enables managing tasks, notes, projects, collections, reviews, and more through typed tools over stdio.
      66
      -

    • @omnidim-ai/mcp-server

      Omnidim
      A
      license
      A
      quality
      B
      maintenance
      Local stdio Model Context Protocol server for OmniDimension. Drive voice agents, dispatch calls, and manage knowledge bases from Claude, Cursor, Windsurf, or any MCP-compatible client.
      52
      141 npm
      7
      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

    A3.5/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources like contacts, calls, messages, phone numbers, users, and webhooks, with clear action distinctions (e.g., create_contact vs. update_contact). However, some potential overlap exists between list_calls and list_conversations, as calls might be part of conversations, which could cause minor confusion for agents.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as create_contact, list_calls, get_user, and send_text. All tools use snake_case with clear verbs (create, delete, get, list, update, send), making them predictable and easy to understand.

    Tool Count4/5

    With 21 tools, the count is slightly high but reasonable for a comprehensive CRM/communication platform like Quo, covering contacts, calls, messages, phone numbers, users, and webhooks. It feels a bit heavy but not excessive, as each tool serves a specific function in the domain.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for the domain, including create, get, list, update, and delete operations for contacts, calls, messages, phone numbers, users, and webhooks. There are no obvious gaps; agents can perform core workflows like managing contacts, handling calls, and sending messages without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources