MCP
MCP gives compatible AI agents controlled access to your live commerce operation. Agents can inspect orders, balances, payouts, customers, products, buy links, messages, and certified analytics, then perform supported merchant actions with your confirmation.
Connect to https://mcp.inttegro.com. This is the complete server URL; do not
append /mcp or use the hosting-provider URL.
Choose your path
| Guide | Use it when you want to |
|---|---|
| Connect a client | Configure ChatGPT, Insomnia, Codex, Claude Code, Cursor, an API connector, or another MCP harness |
| Use the Claude Code plugin | Load Inttegro's five merchant workflows and two read-only specialist agents in Claude Code |
| Build an integration with an agent | Choose an SDK and checkout architecture, produce an agent-ready build brief, and check test readiness |
| Explore the tool catalog | See all 24 read tools, 24 confirmed action tools, three integration-guidance tools, and optional presentation tools |
| Run merchant workflows | Ask analytics questions, inspect operations, create a buy link, or create and invoice an order |
Fastest integration path: connect an MCP client, then ask its agent to use
design_integration. The tool collects the
architecture decisions and returns the initial operations, implementation
steps, documentation, and tests as one agent-ready brief.
What an agent can do
- Answer operational questions about orders, balances, balance activity, payouts, payment settings, products, prices, customers, buy links, and messages.
- Return exact 7, 30, or 90-day order, product, customer, payout, and message analytics without estimating totals from bounded list pages.
- Turn SDK, runtime, and checkout choices into a versioned implementation brief and end-to-end test plan without accepting credentials.
- Create customers, orders, products, prices, and hosted buy links after confirmation.
- Manage supported order, product, price, and buy-link lifecycle changes and send invoices, receipts, SMS messages, or buy links to existing customers after confirmation.
- Add Flint-backed charts and optional MCP Apps views while keeping exact structured values available to every client.
Safety boundaries
The server does not execute payments, move balances, change payout settings, reveal raw customer contact details, accept arbitrary SMS recipients, broadcast messages, or provide a generic proxy to the Commerce API.
Every action requires MCP form confirmation. Read tools minimize sensitive data, money remains authoritative in integer minor units, and values from different currencies are never combined.