Connect your AI agent

Every agent connects to the same server through the same flow: you add a remote MCP server with the Tilopay URL and authorize the session in the browser. The only thing that changes per agent is where you add it.

https://mcp.tilopay.com/mcp

Before connecting#

1. Access is not self-service: the merchant requests it through the MCP server form and Tilopay creates a dedicated user tied to one merchant.
2. That user gets an email invitation and sets a password. It is the account used to authorize the agent.
3. Review what an agent can do before connecting it, especially the tools marked as sensitive.

Claude#

Claude supports remote connectors, both in the desktop app and on the web.

1. Add a remote custom connector with the server URL.
2. Claude opens the Tilopay authorization screen: sign in with the MCP user.
3. Review the consent screen (requesting application, return URL and permissions) and approve.
4. Back in the conversation, the Tilopay tools are available.

There is no token to paste: the connector registers itself.

ChatGPT#

ChatGPT connects as a remote connector using the same URL.

1. Add the server as a remote connector with the URL above.
2. Authorization completes in the browser with the MCP user.
3. Once approved, the connector is active and the model can call the tools.

GitHub Copilot and VS Code#

In VS Code (with Copilot in agent mode) you declare a remote HTTP MCP server.

1. Declare the server with the URL, no token or credentials in the config file.
2. On first use, the editor opens the browser to authorize.
3. After approving, the tools show up in the agent's tool list.

Cursor and other editors#

Cursor and equivalent editors use the same scheme: a remote MCP server over HTTP.

1. Add the remote server with the URL, no token in the configuration.
2. Authorize in the browser when the editor asks.
3. Enable the tools for the editor's chat or agent.

Gemini#

Gemini clients that support remote MCP connect the same way: register the server URL and authorize in the browser. If the client only supports local stdio MCP servers, you need a bridge that speaks Streamable HTTP against the Tilopay URL.

Other MCP clients#

For a custom client or any other agent, the requirement is support for Streamable HTTP transport and OAuth 2.0 with dynamic client registration. The sequence is:

1. The client calls the server and gets a 401 with WWW-Authenticate, pointing to /.well-known/oauth-protected-resource.
2. The client discovers the identity provider endpoints.
3. It registers dynamically and opens the authorization screen.
4. The user signs in and approves the consent screen.
5. The client stays connected with authorization_code and refresh_token.

The only thing you configure is the server URL.

Verify the connection#

Ask the agent to list the available tools: the Tilopay ones should appear, grouped into sales and transactions, payment links, catalog, contacts, recurring billing, stored cards and bulk collections and support and diagnostics.

A safe first test is a read-only query, for example asking for transactions in a date range. For full flows see the recipes.

If something fails#

• The client never opens authorization: check the server is declared as remote over HTTP, not as a local server.
• Authorization never completes: sign in with the dedicated MCP user, not with the Tilopay dashboard user.
• The agent sees no tools: several clients require enabling them for the conversation or for agent mode after connecting.
• A tool returns empty: it may be the queried environment; several tools default to production.