home / mcp / abacate pay mcp server

Abacate Pay MCP Server

Provides multi-tenant MCP access to Abacate Pay actions like customers, invoices, and PIX QR codes.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "abacatepay-abacatepay-mcp": {
      "url": "https://mcp.abacatepay.com/mcp",
      "headers": {
        "MCP_PORT": "8080",
        "ABACATE_PAY_API_KEY": "sua_api_key_aqui"
      }
    }
  }
}

The Abacate Pay MCP Server lets you manage customers, invoices, payments, and related actions through an MCP interface. It supports multi-tenancy so multiple clients can use a single server securely, making it easy to automate payments and reconciliations from chat assistants and automation tools.

How to use

You can use the MCP server with either a local stdio client or via HTTP for automation. In stdio mode, you run the server locally and interact through standard input/output, providing an API key through your client’s environment. In HTTP mode, you send requests to a public or private MCP URL and authenticate with an API key passed in request headers.

With multi-tenancy, different users or organizations can share the same MCP server. Each request can carry its own API key, isolating data by key. You can perform core actions like creating and listing customers, creating invoices and payment links, generating PIX QR Codes for instant payments, applying discount coupons, and simulating payments for development and testing.

How to install

Prerequisites you need on your machine before starting: - Bun installed (version 1.0.0 or newer) – Bun is used to run and install dependencies. - A compatible shell to run commands.

Step 1. Clone the MCP server repository and install dependencies.

git clone https://github.com/AbacatePay/abacatepay-mcp.git
cd abacatepay-mcp
bun install

Configure clients (Claude Desktop and Cursor)

To run the MCP server with Claude Desktop or Cursor, configure the client to start the MCP with the proper command and environment variable for your API key.

{
  "mcpServers": {
    "abacate-pay": {
      "command": "bun",
      "args": ["/caminho/completo/para/abacatepay-mcp/src/index.ts"],
      "env": {
        "ABACATE_PAY_API_KEY": "sua_api_key_aqui"
      }
    }
  }
}

Configure in the Cursor tool

Add a similar configuration in Cursor to start the MCP server with the same API key setup.

{
  "mcp.servers": {
    "abacate-pay": {
      "command": "bun",
      "args": ["/caminho/completo/para/abacatepay-mcp/src/index.ts"],
      "env": {
        "ABACATE_PAY_API_KEY": "sua_api_key_aqui"
      }
    }
  }
}

Public remote server and HTTP usage

If you only need the MCP server for HTTP-based automation, you can use the public server without installing locally.

Public endpoint to start with is the following MCP URL and you will supply your API key in the headers.

Available tools

createCustomer

Create a new customer with details such as name, email, phone, and identification. Used for onboarding customers into Abacate Pay.

createPixQrCode

Generate a PIX QR code for a specified amount and description to enable instant payments.

createInvoice

Create an invoice or payment link for a customer, enabling tracking of payments and settlements.

listCustomers

Retrieve a list of customers registered in the Abacate Pay MCP workspace.

searchCharges

Query and retrieve charge details, useful for investigating transactions and refunds.