Skip to main content
Glama
ampcome-mcps

Square Model Context Protocol Server

by ampcome-mcps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Square Model Context Protocol Server

No user-submitted related servers found.

    Related Servers

    • Spreedly MCP Server by spreedly

      Spreedly MCP Serverofficial

      spreedly
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to manage payments via Spreedly API, including gateways, transactions, and payment method tokenization.
      32
      18 npm
      10
      Apache 2.0

    • squarespace-mcp

      The1Studio
      F
      license
      A
      quality
      C
      maintenance
      Enables LLM agents to interact with Squarespace Commerce APIs (products, orders, inventory, transactions) using natural language.
      11
      -

    • ConsignCloud MCP Server

      modellers
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to manage consignment and retail business operations through the ConsignCloud API, including inventory management, sales tracking, vendor accounts, and analytics.
      26
      1
      GPL 3.0
    • paystack-mcp-server by PaystackOSS

      paystack-mcp-serverofficial

      PaystackOSS
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with the full range of Paystack APIs, allowing operations like transaction management, customer creation, and payments through natural language.
      2
      50 npm
      55
      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 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: get_service_info provides service metadata, get_type_info supplies method type details, and make_api_request handles all actual API calls. The descriptions explicitly state the sequential dependency between them, eliminating any confusion about when to use each tool.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (get_service_info, get_type_info, make_api_request) with clear, descriptive names that reflect their specific functions. The naming is uniform and predictable across the entire set.

    Tool Count3/5

    With only 3 tools, the count feels thin for covering the extensive Square API surface listed (over 40 services). While the tools are well-designed, the minimal number may force agents to rely heavily on a single make_api_request tool for all operations, which could be cumbersome for complex workflows.

    Completeness4/5

    The tool set provides complete coverage for the Square API domain through a unified request tool, with preparatory tools for service and type information. However, the reliance on a single generic API call tool may lack the granularity and error handling that dedicated tools for common operations (like create_order or get_payment) would offer, creating minor gaps in usability.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources