We didn’t build you another AI assistant to learn. We opened a direct line so the AI you already use— Claude, ChatGPT, Copilot — can read and write your live business data in plain English, from the same chat you’re already in. No new tool. No new tab. No exports.
Every other platform’s move is to add a chatbot you have to learn. That’s vendor-centric — it assumes their product deserves your attention. We did the opposite: sparx doesn’t ask for your attention, it makes your business reachable from wherever your attention already is.
No integration project, no consultant. The whole thing is generate a key, paste it once, and start asking.
Turn on the AI module in your dashboard — one click. It gates the MCP server and tracks which modules your AI can reach.
In Settings → AI Integrations, generate a scoped key. Paste it, with the endpoint below, into your assistant once.
In the chat you already use: “What were my top customers this quarter?” Your AI does the rest, live.
mcp.sparx.works/v1Authorization: Bearer sk_live_…The exact config for each client — Claude, ChatGPT, Copilot — is generated with your real key in the dashboard and spelled out step by step in the connection guide.
No dashboards to learn, no exports, no formulas. You ask the way you’d ask a colleague — in the assistant you already use — and it works from your live, up-to-the-minute data.
Your assistant can use the tools for the modules you’ve turned on — and only those. Scopes follow your modules, so the surface grows as you do.
Orders, order stats, unfulfilled queue, top customers, revenue summaries.
Profiles, inactive lists, B2B accounts, pipeline, add a note.
Catalog search, low-stock alerts, per-product performance, adjust inventory.
Delivery and open rates, active automations, send a broadcast to a segment.
Read and update Builder pages, layouts, and published content.
List, trigger, and inspect platform automations and their runs.
Draft and read invoices and quotes — when the Invoicing module is on.
Services, availability, and bookings — create, reschedule, or cancel a booking.
One query across every record — products, customers, content, more.
Opening a line to your data is only worth it if you stay in control of it. Access is scoped, every action is logged, and you can cut it off in a click.
Issue a separate scoped key for each assistant or teammate. They never share one credential.
A key carries exactly the scopes you grant — read-only, a single module, or write where you allow it.
Anything that changes data — an order status, inventory, a send — surfaces a confirmation before it runs.
Tool name, actor, and result land in the audit log. You can see exactly what your AI did, and when.
Kill a key the moment you want to. The line closes instantly — no propagation delay, no leftover access.
A flat per-tenant rate limit blunts runaway loops and accidental bulk actions. It’s a guardrail, not a meter.
MCP is an open standard, so this isn’t a one-vendor bet. The same endpoint and key work in whatever you already use — switch assistants and your connection comes with you.