6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Medidata
Search Medidata product documentation and rank clinical trial sites 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 Medidata connector does
The Medidata MCP server connects Medidata — the clinical trial platform behind Rave EDC — to Claude, ChatGPT and any MCP-compatible agent. It exposes three read-only tools: one searches Medidata's product documentation, and two rank investigator sites for protocol planning. No tool reaches patient data, and none writes to a trial.
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.
Medidata tools (3)
- search_support_documentation
- get_ranked_sites
- get_supported_disease_areas
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- No application scopes exist. The RFC 9728 descriptor and the authorization server both advertise exactly
openid,offlineandoffline_access. Every one is an identity or session claim, so consent draws no boundary between the documentation tool and the site-ranking tool — granting one grants both. With three read-only tools the blast radius is small, but if Medidata adds a write tool later, this consent screen as it stands would not distinguish it. offline_accessmeans the agent can act while you are away. Medidata's own consent screen spells this out as "Access your account when you're not present". A refresh token outlives the session that created it.- The tool lists disagree on one name. Anthropic lists
get_supported_disease_areas; Medidata documentsget_supported_indications. We could not establish which is live because the endpoint is authenticated. - We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so all parameter detail on this page comes from Medidata's documentation rather than from the server.
- Early adoption only. Access is by request to a named Medidata contact, and site ranking requires an Intelligent Trials subscription. Neither is self-serve.
- Claude is the only tested client. Medidata states support for other AI applications is in active development.
- No audit-trail, logging or Part 11 statement covers MCP calls. Confirm with Medidata if your SOPs require one. No documented tool alters trial data, so nothing here changes a Part 11 record.
- No ranking-model accuracy figure is published. Medidata names the model's inputs but no performance metric, and the ranking drives real trial-cost decisions.
- Documentation search returns storage paths, not links. The documented response gives sources as internal
s3://paths, so a cited article may not be one the reader can open directly. - The vendor documentation is a single page. Medidata's MCP bundle contains exactly one topic, last updated 2026-02-07. There is no changelog, versioning or deprecation notice.
Frequently asked questions
Can the Medidata MCP server read patient data from a clinical trial?
No. None of the three tools reaches subject-level data. Medidata documents one tool that searches published product documentation, one that lists therapeutic areas, and one that ranks investigator sites using historical enrollment statistics. No tool names a study, a subject, a visit or a case report form, and no documented parameter accepts a subject identifier.
Can an AI agent change or sign a clinical data point in Rave EDC?
No. All three documented tools are reads, and none writes to Rave EDC at all. No tool creates, updates, signs, locks, freezes or unlocks a record, and no documented parameter takes a form or field value. The connector has no write path into any electronic data capture system, so no MCP call can become a Part 11 audit-trail event.
What OAuth permissions does the Medidata MCP server request?
Only identity and session ones. The server's own RFC 9728 descriptor advertised three scopes on 2026-08-23 — openid, offline and offline_access — and Medidata's consent screenshot shows exactly three matching grants. None names a Medidata product, study or dataset, so consent carries no data boundary and grants nothing beyond sign-in plus refresh.
How many tools does the Medidata MCP server have?
Three, and Medidata says the count will grow. Anthropic's directory and Medidata's documentation both list three, and Medidata states it will add more capabilities over time. The two lists agree on two names exactly but disagree on the third, so one of them is stale — the directory calls it get_supported_disease_areas and the vendor documents get_supported_indications.
Is the Medidata MCP server generally available?
No. Medidata states the MCP server is available through an early adoption program and that access must be requested from a named contact. Site ranking is further limited to Intelligent Trials customers. Medidata also notes the server was tested thoroughly with Claude and that official support for other AI applications is still in active development.
Does the site ranking tool return personal data?
Institutional contact details, not patient data. Medidata's documented response returns site name, street address, city, country, postal code, coordinates, phone number and website for each ranked facility. Those identify research institutions rather than individuals, and one documented example returned 501 rows, so a single call can pull a large contact set.
Are Medidata MCP calls recorded in an audit trail?
Medidata does not say. The MCP documentation describes no logging, no audit trail and no 21 CFR Part 11 or GxP handling for connector calls, and the public Knowledge Hub returns no Part 11 guidance. Because all three tools are reads that never touch trial data, no Part 11 record would be altered — but the logging question itself stays unanswered.
What do I need before connecting Medidata to Claude?
Early-adoption access and standard Medidata credentials. Medidata directs access requests to a named program contact, then the connector appears under Settings, Connectors, Browse Connectors in Claude. You sign in to the Medidata platform and authorize the application. Ranking tools additionally require an Intelligent Trials subscription.
Sources
- Medidata MCP Server Documentation (retrieved 2026-08-23). This is the exact documentation URL Anthropic's directory publishes for this connector.
learn.medidata.com/robots.txtis a blanketDisallow: /, so we made one directed read of that vendor-nominated page and did not crawl the host. The page is a client-rendered Zoomin app whose topic body is absent from the HTML shell — a text extractor scores it at roughly 400 words of chrome. The 1,070-word body was read from the documented backend API,learn-be.medidata.com, whose ownrobots.txtexplicitly carriesAllow: /api/. · retrieved 2026-08-23 - Medidata Privacy Policy, Customer Data versus Platform Products Personal Data (retrieved 2026-08-23) · retrieved 2026-08-23
- Live OAuth posture check: RFC 9728 resource metadata at
https://mcp.imedidata.com/.well-known/oauth-protected-resource, and authorization server metadata athttps://oauth-authorization.platform.imedidata.com/.well-known/oauth-authorization-server(2026-08-23). Four control probes were run: only the canonical resource path returned 200, three sibling and nonsense paths returned an identical 401 body, and thewww-authenticateheader on the endpoint names the same canonical path — so the 200 is a genuine descriptor, not a catch-all. · retrieved 2026-08-23 - Medidata Innovate sandbox descriptor —
https://mcp-innovate.imedidata.com/.well-known/oauth-protected-resource(2026-08-23) · retrieved 2026-08-23 - Consent and sign-in screenshots embedded in Medidata's MCP documentation, read as images (retrieved 2026-08-23). The authorization screen lists three grants — basic profile, offline resources, and account access when not present — corroborating the three advertised scopes. · retrieved 2026-08-23
- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Medidata support — <mailto:helpdesk@mdsol.com> · Privacy
More Productivity connectors
Adobe Experience Manager
Create, edit, publish and delete AEM pages, content fragments and assets from an agent.
Adobe Workfront
Find, create, update and delete Workfront work items from an AI agent.
Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.
Use it in an agent
Put Medidata to work.
Connect Medidata once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.