Give your AI agent access to your Acenda analytics with Acenda MCP.

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. Step 1Type your organization slug in the box on the right.
   The prompt fills it in for you as you type.
2. Step 2Click Copy prompt.
   The whole message — with your slug already in place — is copied for you.
3. Step 3Paste it into your AI assistant and send.
   The assistant walks you through adding the connector in its own current settings screens.
4. Step 4Sign in with your Acenda credentials when asked.
   A browser window opens — use your normal Acenda login. No API keys involved.
5. Step 5Let it run the test query.
   The prompt ends by checking total orders for the last 7 days — if that answers, you’re connected. Some assistants need a paid plan or admin approval for custom connectors; the assistant will tell you if yours does.

Help me connect this assistant to my company’s Acenda MCP server so I can ask questions about our store’s orders, sales, products, marketplaces, and returns.

Connection details
• MCP server URL: https://api.acenda.io/v1/mcp/{{ slugShown }}
• Organization: the identifier at the end of the URL above. If it still says YOUR_ORG, ask me for my Acenda organization identifier before continuing.
• Authentication: OAuth. I sign in through the browser using my normal Acenda credentials. No API keys or manually configured client IDs are required.
• Access: Read-only analytics, limited to the organization specified in the URL.

Make setup easy to follow
Help me keep this conversation visible while I configure the connection in a second window, ideally side by side. If sign-in opens another browser window, explain how to return afterward.

Give me one short, numbered step at a time and wait for me to say “done” or describe what I see before continuing. Put any URL or value I need to copy on its own line in a code block. Keep track of our progress so I can say “resume setup” if I lose my place.

What I need you to do
1. Identify the app I’m using. If you can’t determine it, ask me.
2. Check this app’s current official instructions for adding a custom MCP server, connector, or connected app. Use the exact menu and setting names; don’t guess. If you can’t verify the current interface, say so.
3. Guide me through arranging the two windows, then adding the Acenda connection using the details above. Complete any supported setup actions yourself. Let me enter my credentials and approve OAuth access in the browser; never ask me to paste passwords or tokens into chat.
4. If setup is unavailable, explain the specific limitation and any verified plan, setting, or administrator approval required. Don’t assume an upgrade is necessary.
5. After connection, use the Acenda tools to retrieve total orders in the last 7 days. Report the result, organization, exact date range, and timezone. Confirm success only if the query actually succeeds; otherwise, explain the error and the next troubleshooting step.

3. Paste it into your assistant’s chat

Send it like a normal message.

4. Follow the instructions within your agent

It walks you through connecting and signing in with your Acenda login. If it asks for the connection link again, enter your MCP server URL:

https://api.acenda.io/v1/mcp/{{ slugShown }}

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.

Tested and working: Gemini, Claude, ChatGPT and Grok. Claude Code and Grok Bot are different clients from the Claude and Grok apps and have not been tested yet — they may have compatibility issues. Other MCP-capable assistants that support remote servers with OAuth may also work; see the compatibility list above.