MCP Integration
The plugin that teaches AI agents to integrate Tonder's SDKs using versioned documentation.
tonder-ai-integrations is Tonder's suite
of AI-agent plugins: they help developers integrate Tonder SDKs correctly in their applications,
using versioned documentation instead of the model's memory.
The first available plugin is Tonder Web SDK (tonder-web-sdk), for Claude Code, Claude
Desktop, Codex CLI, and Codex Desktop. It packages two pieces:
- An integration skill (
tonder-web-sdk-integrator) that knows web frameworks and guides the agent step by step. - A local MCP server (
tonder-docs) that serves versioned snapshots of the Web SDK documentation — integration recipes, API reference, errors, and payment statuses. It runs locally over stdio with Node.js: it opens no ports, never calls the Tonder backend, and needs no credentials.
Availability. The plugin can be installed today from the GitHub repository marketplace
(current version: 0.1.7). Publication in the official Claude plugin directory and the Codex
directory is pending.
What it can integrate
| Supported flows | Card payment · Card enrollment · Saved-card payment · Payment methods (e.g. SPEI, OXXO Pay) · SafetyPay banks |
| Frameworks | Vanilla HTML, React, Next.js, Angular, and similar (browser-based web apps) |
| Hosts | Claude Code · Claude Desktop · Codex CLI · Codex Desktop |
How the plugin works
When you ask for an integration, the plugin guides the agent to:
- Inspect your project before editing (it detects the framework and the checkout page).
- Query the
tonder-docsMCP as the only source of truth — it never improvises examples or uses local doc copies. - Ask before deciding: payment flow, presentation mode (embedded or redirect), CDN or npm loading, and default or custom UX.
- Implement the smallest working integration for the chosen framework and flow.
- Validate PCI safety: merchant code never collects raw PAN, CVV, or expiration data — always the SDK-rendered secure fields.
- Remind you of the operational side: API keys,
idempotency_key, webhooks, environment values for production, and backend reconciliation.
The tonder-docs MCP server is bundled inside the plugin — it isn't installed separately. Once
you install the plugin in your editor, the MCP is available automatically.