Skip to main content
Glama
square

Square Model Context Protocol Server

Official
by square
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Square Model Context Protocol Server

No user-submitted related servers found.

    Related Servers

    • AI-Assisted CRM MCP Server

      MdJafirAshraf
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to perform CRM operations like creating contacts, managing deals, and updating leads through natural language using the Model Context Protocol.
      4
      -

    • Relatio CRM MCP Server

      charbelkassab
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage CRM prospects, activities, reminders, and mailbox via natural language commands through the Model Context Protocol.
      3
      MIT
    • @vitrion/zentria-mcp by vitrionbv

      @vitrion/zentria-mcpofficial

      vitrionbv
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to access and manage Zentria CRM data, including sales, customers, to-dos, and more, through the Model Context Protocol.
      80
      14 npm
      MIT
    • Fireblocks MCP Server by fireblocks

      Fireblocks MCP Serverofficial

      fireblocks
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely interact with Fireblocks services through the Model Context Protocol, supporting transaction management, vault and exchange account queries, network connections, and workspace user management.
      16 npm
      10
      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.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct and clearly defined role in the workflow (service info, type info, API request), with no overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_service_info, get_type_info, make_api_request), using snake_case throughout.

    Tool Count4/5

    Three tools is minimal but appropriate for a unified API wrapper, as the tools cover the essential introspection and request workflow.

    Completeness5/5

    The tool set covers the full lifecycle: discover services, get type information, and make API requests. No obvious gaps for the intended purpose.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources