MCP server
Let AI agents and chat automations create real TeePay checkout links and read verified payment status.
TeePay runs a Model Context Protocol server, so AI assistants and automation platforms can sell on your behalf: look up your products, create checkout links and check whether a customer has paid, while TeePay keeps prices, limits and payment confirmation under its control.
| Server | URL | For |
|---|---|---|
| Checkout MCP | https://mcp.teepay.me/checkout/mcp | Sales assistants and WhatsApp automation |
| Merchant MCP | https://mcp.teepay.me/merchant/mcp | Your own tools; adds listing your payment links |
Transport: Streamable HTTP.
Authentication
Agents authenticate with your restricted link key (tplk_…), sent as Authorization: Bearer.
Generate it in Payment links → Settings. A link key can only read your catalog and create or read
payment links. It cannot read balances, send payouts, change prices or act for another merchant.
Regenerating it disconnects every agent using the old key.
Connect a client
{
"mcpServers": {
"teepay": {
"type": "http",
"url": "https://mcp.teepay.me/checkout/mcp",
"headers": { "Authorization": "Bearer ${TEEPAY_LINK_KEY}" }
}
}
}Store the key in the client's secret settings, never in a prompt or chat message. The dashboard page Developers → AI & MCP shows your endpoints and key status.
Limits
- 60 requests per account per minute, shared with the Link API.
- Requests from browsers are rejected; MCP clients must connect from a server or desktop app.