Skip to main content
Glama
macedoflp

Asaas MCP Server

by macedoflp

Related Servers

Alternatives to Asaas MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying and operating Asaas digital account and billing (boletos, PIX, credit card, subscriptions, splits, etc.) via natural language, with read-only access.
      7
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with Conta Azul Financial APIs to manage accounts, balances, and transactions through natural language. It features specialized tools for tracking cash flow, processing payables and receivables, and generating comprehensive financial reports.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables integration with Abacate Pay API for managing payments, customers, and billing through AI assistants. Supports multi-tenancy, PIX QR codes, discount coupons, and payment simulation with secure per-request API key authentication.
      11 npm
      5
      MIT
    • F
      license
      B
      quality
      Not graded
      maintenance
      Enables Claude to interact with the Vaultix Payment API for managing charges, customers, refunds, payment links, payouts, and balance transactions. Supports Brazilian payment methods including PIX, card, and boleto payments.
      32
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to securely create payment references and requests for Multibanco, MB WAY, Payshop, Credit Card, PinPay, Cofidis Pay, PIX, and retrieve payment reports.
      -

    TDQS

    B3.3/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, but get_pix_status and get_payment overlap in checking payment status, and create_pix_qr could be confused with create_payment for Pix charges. Descriptions help clarify, but minor ambiguity remains.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (e.g., create_customer, list_payments, get_pix_status, cancel_subscription). No mixed conventions or vague naming.

    Tool Count4/5

    16 tools is slightly above the ideal 3-15 range, but reasonable for a payment platform covering customers, payments, subscriptions, subaccounts, and webhooks. Each tool earns its place, though some consolidation could be possible.

    Completeness3/5

    Core create/read operations exist for payments and customers, but notable gaps include no update or delete for customers, no get/update for subscriptions, no list/get/update for subaccounts, and no list/delete for webhooks. These omissions could hinder full lifecycle management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues