Addgene
Search Addgene's plasmid and viral prep catalog from Claude.
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
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
security.admin, which no default role includes.set_customer_prompt changes how AskCorral answers for every user of the account, and needs company.edit.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.
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.
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.
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.
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.
llms.txt (retrieved 2026-11-17). Index used to locate the pages above. · retrieved 2026-11-17initialize returning 401 with a Bearer challenge; RFC 9728 descriptor at https://mcp.corraldata.com/.well-known/oauth-protected-resource/mcp; OpenID configuration at https://auth.corraldata.com/realms/corraldata/.well-known/openid-configuration. · retrieved 2026-11-17permissions text. · retrieved 2026-11-17Connect CorralData once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.