> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tagada.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Started

> Connect an AI assistant to your Tagada account and find out why a store is not taking payments.

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.

```text theme={null}
https://api.tagada.io/api/mcp
```

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](/developer-tools/funnels/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

<Tabs>
  <Tab title="Claude Code">
    ```bash theme={null}
    claude mcp add --transport http tagada https://api.tagada.io/api/mcp
    ```

    Then run `/mcp` and pick **tagada** to sign in.
  </Tab>

  <Tab title="Claude (web, desktop, mobile)">
    In **Settings → Connectors**, choose **Add custom connector** and paste:

    ```text theme={null}
    https://api.tagada.io/api/mcp
    ```

    Leave the optional OAuth client fields empty, then sign in when the browser opens. All three surfaces share one connector — adding it once is enough.

    On Team and Enterprise plans, only an owner can add a connector for the whole organisation.
  </Tab>

  <Tab title="Cursor">
    In `.cursor/mcp.json`, or your global Cursor settings:

    ```json theme={null}
    {
      "mcpServers": {
        "tagada": {
          "url": "https://api.tagada.io/api/mcp"
        }
      }
    }
    ```

    Cursor prompts for sign-in the first time a tool is called.
  </Tab>

  <Tab title="Codex">
    ```bash theme={null}
    codex mcp add tagada --url https://api.tagada.io/api/mcp
    codex mcp login tagada
    ```
  </Tab>

  <Tab title="ChatGPT">
    Custom connectors sit behind **developer mode**, which you switch on in ChatGPT's settings. Once it is on, add a custom connector and paste:

    ```text theme={null}
    https://api.tagada.io/api/mcp
    ```

    Developer mode is a web-app feature and needs a paid plan. On Business and Enterprise workspaces, an admin may have to allow connected data before it appears.
  </Tab>

  <Tab title="Other clients">
    Any client speaking **Streamable HTTP** with **OAuth 2.1** works, usually with the same JSON:

    ```json theme={null}
    {
      "mcpServers": {
        "tagada": {
          "url": "https://api.tagada.io/api/mcp"
        }
      }
    }
    ```
  </Tab>
</Tabs>

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

<AccordionGroup>
  <Accordion title="No Tagada tools appear">
    Restart the client after saving its MCP configuration. Most clients only read their config at startup.
  </Accordion>

  <Accordion title="'This login is not linked to any Tagada account'">
    Your user is not a member of any organisation. Ask an admin to invite you, then reconnect.
  </Accordion>

  <Accordion title="'Store not found, or not reachable with this authorization'">
    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.
  </Accordion>

  <Accordion title="'Your role on … does not grant …'">
    The tool needs a permission your role lacks — `check_payment` needs processor-read rights. Ask an admin to widen your role.
  </Accordion>

  <Accordion title="'Rate limit exceeded'">
    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.
  </Accordion>
</AccordionGroup>

## Next

<CardGroup cols={2}>
  <Card title="Prompt Library" icon="lightbulb" href="/developer-tools/crm-mcp/examples">
    Three prompts, ready to copy.
  </Card>

  <Card title="Tools Reference" icon="wrench" href="/developer-tools/crm-mcp/tools-reference">
    The nine tools, what they report, and the one that writes.
  </Card>
</CardGroup>