Kushki Docs MCP Server

Connect your AI assistant to the official Kushki product documentation.

AI assistants have become a key tool for speeding up payment integrations. That is why, at Kushki, we publish our product documentation as an MCP server. This way, tools like Claude or Cursor read our current guides, tutorials, and configuration steps directly, instead of relying on their prior knowledge or on fragments you copy by hand.

In this guide, you will learn what MCP is, what you can query through it, how to connect it to your AI assistant, and how to take advantage of it in your Kushki integration.

Keep in mind

This server only exposes our public documentation. You do not need Kushki credentials to use it. The first time it connects, your assistant completes an automatic authorization handshake with the server: there is no login form and you are not asked for any data. Some assistants open a browser tab for a moment, or show a one-time Connect or Authenticate button. The handshake has no consent screen by design: since the server only serves public documentation, there is nothing to grant access to.

What is MCP?

MCP (Model Context Protocol) is an open protocol that connects AI assistants with external data sources. It works as a standardized communication channel: the assistant queries the information directly at the source, and returns answers based on what the documentation says today.

At Kushki, we publish a single remote MCP server that covers the product documentation of our five markets: Mexico, Peru, Colombia, Ecuador, and Chile, in both Spanish and English. The server reads the guides published on our documentation portal: how each payment method works, step-by-step integration tutorials, our payment forms and SDKs, webhooks, and the configuration of the Administration Console. As a result, the AI explains flows, answers product questions, and guides you through the integration based on the current version of the documentation.

This is the address of the Kushki Docs MCP server:

https://mcp.kushki-docs.workers.dev/

The server uses the Streamable HTTP transport, the current standard for remote MCP servers. Your assistant connects to that URL directly, without installing anything.

Looking for the API reference?

This server covers our product and integration guides. To query endpoints, schemas, and request parameters, also connect the Kushki MCP Server for the API reference. Both servers work together: one explains how to integrate, and the other details what each endpoint expects.

Update frequency

The MCP server syncs with our documentation portal every 24 hours. If we publish a change to the documentation, it can take up to a day to be reflected in the server's answers. For very recent updates, check the corresponding guide in our documentation portal.

What you can query

The server indexes the guides published on docs.kushki.com for the five countries, in Spanish and English: payment methods, integration tutorials, payment forms and SDKs, notifications and webhooks, and the Administration Console. It does not include the technical API reference (that is what the other server is for), nor your account data, transactions, or anything behind a login.

Your assistant sees two tools on the server:

Tool	What it does
`Docs-AN___Retrieve`	Searches the guides and returns the fragments most relevant to a question. Each fragment includes the country it belongs to, the portal section, the content type (concept or tutorial), the URL of the original page, and a relevance score. This is the tool your assistant uses to answer your prompts.
`x_amz_bedrock_agentcore_search`	Lets the assistant discover which tools the server offers. It is used internally during the connection, and you do not need to call it.

You do not call these tools yourself: you write a question in the chat and the assistant decides when to use them. For reference, this is an abbreviated example of what Docs-AN___Retrieve returns for the question "how to configure a webhook in Kushki Colombia":

{
  "retrievalResults": [
    {
      "content": {
        "text": "# Notificaciones — ¿Cómo configurar un webhook?\n- **País:** Colombia (co)\n- **Producto / sección:** Notificaciones\n- **Tipo:** tutorial\n- **URL:** https://docs.kushki.com/co/...",
        "type": "TEXT"
      },
      "metadata": { "country": "co" },
      "score": 0.8612
    },
    {
      "content": {
        "text": "# Webhooks — ¿Cómo configurar un webhook?\n- **País:** Chile (cl)\n- **Producto / sección:** Notificaciones > Webhooks\n- **Tipo:** concepto\n- **URL:** https://docs.kushki.com/cl/...",
        "type": "TEXT"
      },
      "metadata": { "country": "cl" },
      "score": 0.7431
    }
  ]
}

The assistant reads those fragments, keeps the ones for the country you mentioned, and writes the answer in the language you use in the chat. Since each fragment includes the URL of the original page, you can ask the assistant to link you to the full guide.

Always name the country

The search covers the guides of all five markets at once. If your prompt does not mention a country, the results bring back one version of the guide per country, and the assistant may mix steps or requirements that do not apply to your market. Include the country in every prompt, for example "Kushki Colombia" or "Kushki Mexico".

Prerequisites

Before you begin, make sure you have the following:

An MCP-compatible AI assistant, such as Claude, Claude Code, Cursor, VS Code, or Cline.

The latest version of that assistant. Support for remote servers is included in current versions and keeps improving with each release.

An internet connection, since your assistant queries the documentation in real time.

An MCP server is a data source, not an assistant: it has no interface of its own. Connecting it only gives your assistant access to our documentation, so you always query it from the chat of the tool you already use.

Connect your assistant

Find your tool in the tabs below and follow its steps. Every route connects to the same server and gives you the same information, and you only need to configure it once: the URL stays in sync with the published documentation, so your assistant will access the most recent synced version without any changes to your configuration.

The menu names in each tool change from one version to another. If a step does not match what you see on screen, the official documentation linked in each tab has the current steps.

Claude

Claude Code

Cursor

VS Code

Cline

Other assistants

In Claude, you add the server as a custom connector. This works both in Claude Desktop and in claude.ai, and it does not require you to edit files or install anything.

Follow these steps:

Open the connectors section of your Claude settings.

Choose the option to add a custom connector.

In the Name field, enter Kushki Docs.

In the URL field, paste the address of the Kushki Docs MCP server.

Confirm with Add. Claude completes the authorization on its own and the connector appears in the list as available.

Open a new chat, display the connectors menu, and check that Kushki Docs is enabled.

In Team and Enterprise organizations, an owner adds the connector from the organization settings, and then each member enables it from their own connectors page. The number of custom connectors available depends on your Claude plan; check the official guide on custom connectors for the current details.

If your file already contains other MCP servers

If the configuration file already contains other servers, add only the inner block "kushki-docs": { ... }, separated from the previous server by a comma, and keep the block of your own tool.

Important

Keep a single main key in the file. If you duplicate it, the JSON will become invalid and your assistant will ignore the entire configuration.

For example, this is how the file looks with both Kushki servers connected, the API reference and the product documentation:

{
  "mcpServers": {
    "kushki-apis": {
      "type": "http",
      "url": "https://apidocs-mcp.kushki-docs.workers.dev/"
    },
    "kushki-docs": {
      "type": "http",
      "url": "https://mcp.kushki-docs.workers.dev/"
    }
  }
}

Verify your connection

To confirm that everything works, ask your assistant a test question, for example: "Using the Kushki Docs MCP server, explain how to configure a webhook in Kushki Colombia." If the answer returns correct information about Kushki, the connection was successful.

If your assistant does not respond with information from our documentation, first check whether the server itself is healthy, and then review the points below.

Check that the server is healthy

Run the following command in your terminal, or open the address in your browser:

The expected response is status: ok with the list of tools. It means the server performed a real query against its backend and the documentation is available, so any remaining problem is in your local configuration:

{"status":"ok","tools":["x_amz_bedrock_agentcore_search","Docs-AN___Retrieve"],"latency_ms":359}

If the response has a different status, or the command returns an error, the problem is on our side and not in your configuration. Wait a few minutes and try again; our team receives an automatic alert when the server is down.

The server does not appear in the list

Quit the assistant completely and open it again. Editing the configuration file is not enough, because the servers load at startup.

The assistant reports a configuration error

Review that the main key appears only once, that a comma separates each block, and that no quotation marks are missing. An invalid JSON file makes the assistant ignore the entire configuration.

Also check that you copied the block from the tab of your own tool. The name of the main key and the value of the type field are not interchangeable between assistants.

The server appears as pending authorization

Select the server in your assistant's MCP panel and confirm the authorization. It is an automatic handshake that does not ask you for credentials.

If you connected the server with mcp-remote and it stops responding, delete the ~/.mcp-auth folder and restart your assistant so it repeats the handshake.

The server connects but does not respond

If the server appears as connected but every question fails, returns an error, or comes back empty, run the health check described above. A status other than ok confirms that the server is the one failing. If the health check is fine, remove the server from your assistant, add it again, and repeat the authorization.

The assistant answers without using the server

Mention the server explicitly in your prompt, for example: "Using the Kushki Docs MCP server, look up...".

The connection fails from your network

If the health check returns a timeout or a network error instead of a response, your network is blocking the connection. Review your network's outbound rules and make sure that HTTPS traffic to mcp.kushki-docs.workers.dev is allowed.

Use cases with Kushki

Once the MCP server is connected, your AI assistant works with our real product documentation. Always mention the country in your prompts: the search covers all five markets, and without a country the assistant can mix steps or requirements from different ones. You can write your questions in Spanish or in English. These are some prompts you can use as a starting point:

Understand a payment method

"According to the Kushki Docs, how do wire transfer payments with PSE work in Colombia, and what is the difference between PSE and PSE Avanza?"

Follow an integration step by step

"Using the Kushki Docs MCP server, guide me step by step to integrate a Kajita payment form in my website's front end for Kushki Mexico."

Configure notifications

"Explain how to configure a webhook in Kushki Mexico and which events I can subscribe to."

Choose an integration option

"Based on the Kushki Docs, what options do I have to accept card payments in Kushki Peru, and which one fits a mobile app best?"

Set up the Administration Console

"Look up in the Kushki Docs where to find my credentials in the Kushki Chile Administration Console and how to switch between test and production environments."

Compare countries

"Compare the cash payment options available in Kushki Ecuador and in Kushki Chile, and tell me the differences."

Combine it with the API reference

"Using the Kushki Docs, explain the card payment flow in Kushki Peru. Then, using the Kushki MCP server for the API reference, generate the Node.js code for each step."

The assistant answers based on our documentation, but it does not replace it. Before going live, validate the fields and flows of your integration against the guides and the API reference of the corresponding country.

With this connection, your assistant stops guessing and starts building on our official documentation. Start integrating Kushki with the help of AI and reduce the development time of your payment solution.

Kushki Docs

Explore our product guides and integration tutorials for each market.

Kushki Developers

Check the API reference of each country.

Model Context Protocol

Learn how the open protocol behind this integration works.

Kushki Docs MCP Server

What is MCP?#

What you can query#

Prerequisites#

Connect your assistant#

If your file already contains other MCP servers#

Verify your connection#

Check that the server is healthy#

The server does not appear in the list#

The assistant reports a configuration error#

The server appears as pending authorization#

The server connects but does not respond#

The assistant answers without using the server#

The connection fails from your network#

Use cases with Kushki#