Skip to main content
The Tagada Config MCP lets an AI assistant inspect how your stores are configured. The setup checklist in the CRM marks a step completed as soon as the record exists; these tools tell you whether it actually works — a processor can be saved and archived, and the checklist counts it either way.
Nothing to install, no API key. The surface is limited to configuration — no orders, no customers, no payments. Eight of the nine tools only read; the ninth, canvas_apply, edits a funnel through the canvas and nothing else. The assistant sees exactly what your CRM role lets you see, across every organisation you belong to, and it can only change what your role lets you change.

Connect your client

Then run /mcp and pick tagada to sign in.
Your client should now list the server tagada-crm-config and its nine tools. Staging accounts use https://api.tagada.dev/api/mcp instead.

Troubleshooting

Restart the client after saving its MCP configuration. Most clients only read their config at startup.
Your user is not a member of any organisation. Ask an admin to invite you, then reconnect.
Either the store id is wrong, or it belongs to an organisation you are not a member of — the message is deliberately the same in both cases. Run list_stores for the ids you can reach.
The tool needs a permission your role lacks — check_payment needs processor-read rights. Ask an admin to widen your role.
You passed 120 tool calls in a minute. Wait for the delay in the Retry-After header. Your API keys are on a separate budget.

Next

Prompt Library

Three prompts, ready to copy.

Tools Reference

The nine tools, what they report, and the one that writes.