> This is Payabli documentation. For a complete page index, fetch https://docs.payabli.com/llms.txt — append .md to any page URL for lightweight markdown. For section-level indexes, query parameters, and other AI-optimized access methods, see https://docs.payabli.com/ai-agents.md # Payabli MCP server overview > Understand how the Payabli MCP server gives your AI tools access to your organization's payments data The Payabli MCP server connects AI tools, such as Claude and Cursor, to your organization's Payabli data. You can ask your AI tool questions in plain language about Pay In and Pay Out activity, such as transactions, disputes, payouts, bills, and vendors. The server uses the Model Context Protocol (MCP), an open standard for connecting AI tools to external data sources. To learn more about the standard, see the [Model Context Protocol introduction](https://modelcontextprotocol.io/introduction). Amigo™ answers questions inside the Payabli Portal. The MCP server gives you access to similar data in your own AI tool. To learn more about Amigo™, see [Amigo Insights overview](/guides/platform-amigo-overview). This server is different from the docs MCP server, which searches Payabli's documentation and doesn't access account data. To search the docs from your AI tool, see [Use the docs MCP server](/developers/platform-developer-mcp). ## What you can ask about The server provides a set of tools. Each tool reads one type of data from your organization. Your AI tool selects the correct tool based on your question, so you don't need to name it. If your AI tool asks for permission before it runs a tool, the request shows the tool name. ### Pay In These tools read the payments that your merchants collect from their customers. | Data | What it returns | Tool name | | ------------- | ------------------------------------------------------------------------------------------------------------ | -------------------------- | | Transactions | Card and ACH payments, with amounts, status, risk status, gateway response codes, and masked payment details | `list_payin_transactions` | | Card disputes | Chargebacks and retrieval requests, with reason codes, amounts, and response deadlines | `list_card_disputes` | | ACH returns | Returned ACH payments, with return reason codes and amounts | `list_payin_ach_returns` | | Subscriptions | Recurring payments from customers, with frequency, amounts, and schedule | `list_payin_subscriptions` | | Batches | Settlement batches, with amounts, dates, and status | `list_payin_batches` | | Transfers | Deposits to merchant bank accounts, with amounts, fees, status, and event history | `list_payin_transfers` | | Customers | Customer records, with IDs, status, balance, and consent settings | `list_customers` | ### Pay Out These tools read the payments that your organization sends to vendors. | Data | What it returns | Tool name | | ------------------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------- | | Payouts | Payouts to vendors, with amounts, status, payment method, vendor, and the bills that each payout paid | `list_payout_transactions` | | Batches | Payout batches, with totals by payment method and status | `list_payout_batches` | | Transfers | Bank transfers that fund payout batches, with amounts, returns, holds, and fees | `list_payout_transfers` | | Vendors | Vendors, with vendor IDs, vendor numbers, business names, status, location, and bill totals | `list_vendors` | | Bills | Vendor bills, with status, vendor, amount, dates, and the payout that paid each bill | `list_bills` | | Scheduled payouts | Recurring payouts to vendors, with frequency, amount, and next run date | `list_payout_subscriptions` | | Virtual cards | Single-use cards and ghost cards issued to pay vendors, with status, amount, and balance | `list_virtual_cards` | | Virtual card transactions | Authorizations, settlements, declines, and returns on virtual cards | `list_virtual_card_transactions` | ### Organizations and paypoints These tools read your organization's structure and account details. | Data | What it returns | Tool name | | ---------------------- | ----------------------------------------------------------------------------------------------- | ------------------------ | | Signed-in organization | The ID, name, and entry name of the organization that you signed in to | `get_my_context` | | Organization tree | Your full organization hierarchy, with the number of organizations and paypoints in each branch | `get_org_tree` | | Sub-organizations | The organizations directly under an organization | `list_sub_organizations` | | Organization details | An organization's name, entry name, services, and summary statistics | `get_organization` | | Paypoints | Paypoints, with name, status, location, and boarding profile | `list_paypoints` | | Paypoint details | A paypoint's name, status, business contact information, and settings | `get_paypoint` | The server also has a `ping` tool that checks the connection. It doesn't return any Payabli data. Every tool reads data without changing it. The MCP server can't create, change, or delete anything in your Payabli account. ## How access works To connect, you sign in to Payabli from your AI tool. Use the same email, password, and multi-factor authentication (MFA) that you use for the Payabli Portal. Your AI tool never sees your password. After you sign in, the MCP server stores your Payabli session and gives your AI tool a separate token. This token works only with the MCP server. The server makes each request as your Payabli user. It returns only the data that your user can already see, and your role's permissions apply to every request. Access is at the organization level. The MCP server doesn't support paypoint-level users. By default, every question is about the organization that you signed in to, so you don't need to enter its ID. Results include all of its sub-organizations, and each record shows which organization it belongs to. To ask about one sub-organization, name it in your question. Your session lasts up to 24 hours. After it ends, your AI tool asks you to sign in again. To connect the Payabli MCP server to your company's own AI agent or chatbot, contact your Payabli representative. ## Data removed from responses Before a response reaches your AI tool, the MCP server removes these sensitive fields from it: * Customer and payor names and contact details, such as street addresses, emails, and phone numbers * Vendor contact details, addresses, tax IDs, and stored payment methods * Paypoint tax IDs and owner details * Bank account details * Full card and account numbers. Responses include masked values, such as `4XXXXXXXXXXX1413`. * Virtual card numbers, tokens, security codes, and expiration dates * User account details on organizations These fields never appear in your AI conversation. Customer records still include the customer ID, state, and country. Use the customer ID to find the customer in the Payabli Portal. You can't search for customers by name or email. The rest of each response, such as amounts, dates, and masked card numbers, goes to your AI tool. Your AI provider's data policies apply to that data. Before you connect, confirm that your organization allows payments data in the AI tool that you use. ## Limits to know If you don't include a date range, a question about Pay In transactions returns only transactions from the last 60 days. To include older transactions, add a date range, such as "since May 1" or "in Q2 2026". AI tools can make mistakes when they read or summarize data. Before you make a decision based on a number, confirm the number in the Payabli Portal. ## Related resources See these related resources to help you get the most out of Payabli. #### Next steps * **[Connect your AI tool to Payabli](/guides/platform-portal-mcp-server-connect)** - Learn how to add the Payabli MCP server to your AI tool and sign in #### References * **[User roles overview](/guides/pay-ops-roles-permissions-overview)** - Explains how user roles and organization scope work in Payabli #### Related topics * **[Amigo Insights overview](/guides/platform-amigo-overview)** - Understand how Amigo, Payabli's AI agent, answers analytics and account questions in natural language * **[Use the docs MCP server](/developers/platform-developer-mcp)** - Learn how to use the docs MCP server to search Payabli documentation from your AI tools