Connect your AI assistant to your Acenda analytics.

MCP server URL

https://api.acenda.io/v1/mcp/your_org {{ copyUrlLabel }}

One prompt works in every assistant.

AI assistants change their settings screens constantly, so step-by-step screenshots go stale fast. Instead, copy the prompt on the right, paste it into your assistant, and it will walk you through connecting in its own current interface.

1. 1Copy the prompt on the right.
   Click Copy prompt — the whole message is copied for you.
2. 2Replace YOUR_ORG with your organization slug.
   It’s the part right after the domain in your Acenda admin URL (https://admin.acenda.io/your_org). Edit it in the pasted text before sending.
3. 3Paste it into your AI assistant and send.
   The assistant reads the details and walks you through adding the connector in its own current settings screens.
4. 4Sign in with your Acenda credentials when asked.
   A browser window opens for sign-in — use your normal Acenda login and approve access. No API keys involved.
5. 5Let it run the test query.
   The prompt ends by asking the assistant to check total orders for the last 7 days — if that answers, you’re connected. Note: some assistants require a paid plan or workspace-admin approval for custom connectors; the assistant will tell you if yours does.

I want to connect this assistant to my company’s Acenda MCP server so it can answer questions about our store — orders, sales, products, marketplaces, and returns.

Server details:
• MCP server URL: https://api.acenda.io/v1/mcp/YOUR_ORG
  (replace YOUR_ORG with our organization slug — the part right after the domain in our Acenda admin URL: https://admin.acenda.io/YOUR_ORG)
• Authentication: OAuth — sign-in happens in the browser with my normal Acenda credentials; there are no API keys or client IDs to configure.
• Access is read-only analytics, scoped to that one organization.

Please walk me through adding this as a custom MCP connector / connected app in THIS app’s current interface, step by step. If this app doesn’t support custom MCP servers on my plan, tell me what plan or setting I need. Once connected, run a quick test query like “total orders in the last 7 days” to confirm it works.

“What were my sales by marketplace last month?”

“Top 10 products by revenue this quarter — and how do returns compare?”

“How is average order value trending week over week?”

Your Acenda account needs access to the organization in the URL. If you can’t open that organization in the Acenda admin, contact your Acenda representative, then reconnect.

The short name of your organization — the part right after the domain in the Acenda admin. The URL must include it: the assistant is scoped to exactly that organization and can’t switch organizations mid-chat.

Most assistants gate custom MCP servers behind a paid plan, a developer setting, or workspace-admin approval. Paste the prompt above and the assistant will tell you exactly what to enable on your plan.

Access tokens expire periodically. Open the assistant’s connector settings and reconnect — you’ll go through the same Acenda sign-in again.

Access is read-only analytics, scoped to one organization, and every query runs as you — with the same permissions your Acenda account has. Nothing can be created, changed, or deleted through this connection. Disconnect any time from the assistant’s settings.

Any assistant that supports remote MCP servers with OAuth — including Claude, ChatGPT, Gemini, and Grok today, and new ones as they add MCP support. That’s why one URL and one prompt beat per-app instructions.

MCP disclaimer