Skip to main content
Glama

Related Servers

Alternatives to klarna-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude and other MCP clients to query live online-store product, order, sales, stock, and customer data in plain English, with secure read-only defaults, masked customer information, capped results, and audit logging.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to manage orders, stock, purchase orders, pickwaves, and channel listings in a user's own e-commerce account through 104 MCP tools, with dry-run defaults for writes.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients such as Claude Code, Claude Desktop, and Cursor to read a user's own Open Finance Brasil data through Meu Pluggy — accounts, balances, transactions, card bills, investments, and spending by category — while remaining strictly read-only and never moving money or storing data.
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables sellers to interact with Amazon Selling Partner API and Advertising API data—orders, inventory, pricing, ads, reports, and more—through MCP clients like Claude and Cursor.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude, ChatGPT and other MCP clients to read an Amiqus ID account—clients, onboarding records and steps, check results, templates, case status counts and webhooks—and, when writes are enabled, create records.
      9
      MIT

    TDQS

    A3.8/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target distinct resources (disputes, sessions, orders, captures, refunds, payouts, transactions). The main ambiguity is the payout cluster: get_payout_report_csv (one payout) vs get_payouts_summary_report_csv (range report) and list_payouts vs get_payout_summary differ by subtle wording. Descriptions mostly disambiguate, but the CSV pair could be misselected at a glance.

    Naming Consistency5/5

    Names follow a consistent get_/list_ verb_noun pattern across the set (list_disputes, get_dispute, get_order, list_captures, get_capture, get_refund, list_payouts, etc.). The only minor wrinkle is payout (singular) vs payouts (plural) in the summary/report names, but conventions remain predictable.

    Tool Count5/5

    13 tools is well-scoped for a Klarna merchant domain spanning disputes, payments sessions, orders, captures, refunds, payouts and settlement reports. Each tool maps to a distinct operation and none feels redundant or filler.

    Completeness3/5

    Read coverage is broad, but the surface is entirely read-only: there are no order creation, capture, refund, cancel or release operations, and disputes expose no actions (submit evidence, represent, arbitrate). This leaves obvious lifecycle gaps for a merchant integration, though it may be intentional for reconciliation-focused use.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues