# Getting Started ## Getting Started Once connected, you can ask Claude things like "What were our top locations by revenue last month?" or "Build me a dashboard comparing provider performance across locations" — and Claude will pull directly from your CorralData account to answer. *** ### Method 1: Claude.ai Connector (Recommended) This is the easiest way to connect. You'll add CorralData directly inside Claude.ai. {% hint style="info" %} You'll need **admin access** to your Claude.ai organization to complete this setup. {% endhint %} **Step 1 — Open your Claude.ai Organization Settings** Log in to [claude.ai](https://claude.ai), click your organization name in the upper left, and select **Settings**. **Step 2 — Go to Connectors** In the left sidebar, click **Connectors**. Scroll down and click **Add Custom Connector**. **Step 3 — Fill in the connection details** Enter the following values exactly as shown: | Field | Value | | ------------------- | ---------------------------------- | | Name | CorralData | | URL | `https://mcp.corraldata.com/mcp` | | OAuth Client ID | `corral-mcp-client` | | OAuth Client Secret | `iAu9n27mfuS8RrMv7iVCVqp801Hi6xqi` | {% hint style="info" %} **Why is the client secret visible here?** These credentials identify the CorralData app to Claude — they don't grant access to your data on their own. Your CorralData login is what actually controls access. Think of it like a public app ID, not a password. {% endhint %} **Step 4 — Click Add** CorralData will now appear in your connectors list. {% hint style="success" %} You're done! CorralData will be available in new Claude conversations. Claude will have access to all accounts your login can view. {% endhint %} *** ### Method 2: Claude Desktop Config File If you're using Claude Desktop on your computer rather than the website, you'll connect by editing a configuration file. {% hint style="warning" %} This is more technical. If you're not comfortable with it, ask your IT person or use Method 1 above. You'll also need Node.js installed — download it at [nodejs.org](https://nodejs.org) if you're not sure. {% endhint %} #### Step 1 — Find your config file The location depends on your operating system: {% tabs %} {% tab title="Mac" %} ``` ~/Library/Application Support/Claude/claude_desktop_config.json ``` {% endtab %} {% tab title="Windows" %} ``` %APPDATA%\Claude\claude_desktop_config.json ``` {% endtab %} {% endtabs %} If the file doesn't exist yet, create it. If it already exists, add the CorralData entry inside the existing `"mcpServers"` block. #### Option A — Access all your accounts Use this if you manage multiple CorralData customers. ```json { "mcpServers": { "CorralData": { "command": "npx", "args": [ "mcp-remote@latest", "https://mcp.corraldata.com/mcp", "--static-oauth-client-info", "{\"client_id\":\"corral-mcp-client\",\"client_secret\":\"iAu9n27mfuS8RrMv7iVCVqp801Hi6xqi\"}", "--static-oauth-client-metadata", "{\"scope\":\"openid mcp:tools\"}" ] } } } ``` #### Option B — Access one specific account Use this if you want Claude to only see one CorralData customer. First, find your customer ID by logging in to CorralData and looking at the URL: ``` https://app.corraldata.com/your-customer-id/ ``` Then paste it into the config below where it says `your-customer-id`: ```json { "mcpServers": { "CorralData": { "command": "npx", "args": [ "mcp-remote@latest", "https://mcp.corraldata.com/mcp", "--header", "X-Corral-Customer: your-customer-id", "--static-oauth-client-info", "{\"client_id\":\"corral-mcp-client\",\"client_secret\":\"iAu9n27mfuS8RrMv7iVCVqp801Hi6xqi\"}", "--static-oauth-client-metadata", "{\"scope\":\"openid mcp:tools\"}" ] } } } ``` {% hint style="warning" %} After saving, fully quit and restart Claude Desktop. Changes don't take effect until you do. {% endhint %} *** ### Your first conversation After connecting, try asking Claude: > "What databases and schemas are available in my CorralData account?" Claude will use the `list_schemas` tool to discover your data. From there you can explore further: > "Show me the tables in the public schema" > "Describe the customers table — what columns does it have?" > "Write a SQL query to find the top 10 customers by revenue this month" *** ### Understanding permissions What you can do depends on your role in CorralData: | Permission level | What you can do | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------- | | **All authenticated users** | Explore schemas, tables, and relationships. Execute read-only SQL queries. View boards, widgets, filters, and datasets. | | **board.edit role** | All of the above, plus create and update boards and board filters. | | **widget.edit role** | All of the above, plus create and update widgets and datasets. | If you try an action you don't have permission for, Claude will let you know. Contact your CorralData administrator to request additional roles. *** ### Tips for effective use * **Start with schema exploration** — Ask Claude to list schemas and describe tables before writing queries. This helps it understand your data model and write accurate SQL. * **Use progressive disclosure** — Ask for a list of boards first, then drill into a specific one. This keeps responses concise. * **Be specific with SQL** — When asking for data, mention the table names and columns you're interested in. * **Leverage filters** — When listing boards or widgets, mention the name or keyword you're looking for to narrow results. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.corraldata.com/kb/mcp/getting-started.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.