CorralData

Query your CorralData warehouse and build dashboards from an AI agent.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the CorralData connector does

The CorralData MCP server connects CorralData, an analytics platform that pulls clinic, CRM, billing and ad data into one warehouse, to Claude and other MCP clients. CorralData documents 61 tools for exploring schemas, running read-only SQL, and building boards, widgets and Data Apps. Sign-in is OAuth, and your CorralData role decides what each tool may do.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

CorralData tools (61)

  • execute_sql
  • get_query_context
  • search_tables
  • list_tables
  • list_schemas
  • describe_table
  • describe_tables
  • get_relationships
  • get_column_values
  • lint_sql
  • validate_widget_query
  • list_boards
  • get_board
  • create_board
  • update_board
  • duplicate_board
  • list_widgets
  • get_widget
  • create_widget
  • update_widget
  • bulk_update_widgets
  • list_board_filters
  • get_board_filter
  • create_board_filter
  • update_board_filter
  • delete_board_filter
  • list_datasets
  • create_dataset
  • update_dataset
  • create_data_app
  • list_prompts
  • get_prompt
  • list_customers
  • list_services
  • search_service_tools
  • call_service_tool
  • reorder_board
  • screenshot_widget
  • set_customer_prompt
  • update_data_app

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • PHI leaves CorralData's BAA when it reaches your AI tool. CorralData states its BAA does not cover a connected AI tool. Patient-level questions need your own BAA with the AI provider.
  • Read-only SQL is CorralData's claim. CorralData documents query execution as read-only with configurable row limits. We did not test it, because that needs a login.
  • Changes inside CorralData are real. Board, widget, dataset, filter and row-level security tools change live content, and four are labelled permanent deletes. Apart from connected-service writes, the only confirmation is your client's approval prompt.
  • Row-level security edits change who sees patient rows. Those tools need security.admin, which no default role includes.
  • Account-wide AI instructions are writable. set_customer_prompt changes how AskCorral answers for every user of the account, and needs company.edit.
  • Result size is capped. Query results return up to 10,000 rows, with 1,000 by default, per CorralData.
  • The directory understates the surface. It lists 40 of the 61 documented tools.
  • Multi-account logins need care. CorralData says the AI tool can reach every account your login can view, and recommends confirming which one you are working in.
  • No schema or annotation detail from us. The handshake was refused without credentials, so the tool detail on this page comes from CorralData's documentation.

Frequently asked questions

Is the CorralData MCP connector HIPAA compliant?

Not on its own, and CorralData says so. Its HIPAA page states that a connector is not HIPAA compliant by itself, because compliance comes from the agreements in place and how data is protected. CorralData describes itself as HIPAA compliant with a BAA on every plan, but patient-level results sent to your AI tool need your organization's own BAA with that AI provider.

Does CorralData's BAA cover my own AI tool?

No. CorralData's HIPAA page says its BAA covers the warehouse, boards, exports and AskCorral, its in-app AI agent, but does not extend to an AI tool you connect through the MCP connector. That tool runs under your own agreement with your AI provider. CorralData's advice is to ask patient-level questions in AskCorral unless you hold your own BAA with the provider.

Can my AI tool change our data through CorralData?

Not the warehouse data, according to CorralData. Its HIPAA page says the connector can view your data but cannot edit, move or delete anything in the warehouse. Depending on your role, the AI tool can create and edit boards, widgets, filters, datasets and Data Apps inside CorralData, and run actions in connected services such as CRMs after you approve each one.

Why can't I run SQL through the CorralData connector?

Because your CorralData role lacks the sql.execute permission. CorralData's authentication docs say Viewer and Reports Only roles cannot run SQL through the MCP server. Running queries, describing tables and reading column values need the Editor or Admin role, or a custom role that includes sql.execute. Listing schemas and tables, searching and viewing relationships work for every role.

Do I need a client secret to connect CorralData?

No. CorralData uses a public OAuth client, corral-mcp-client, protected by PKCE, so there is no secret to keep. Its setup guide says that if a form insists on a client secret, enter any value, because it is not checked. Your own CorralData login decides what data you can see, not the client ID, and a client ID alone grants no access.

Sources

Use it in an agent

Put CorralData to work.

Connect CorralData once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.