API & MCP INTEGRATION

Connect MBRS to your AI workflow.

Use the MBRS remote Model Context Protocol (MCP) connector to access authorized biological diligence information from Claude. Your existing MBRS account permissions continue to control what you can see or submit.

Connect your approved MBRS account

Connect MBRS to Claude

Open Claude with the MBRS connector name and server address already filled in. Review the connection and sign in to MBRS when prompted.

Connect MBRS to Claude ↗

Claude will ask you to review and approve the connector. If you must sign in to Claude first, return here and click the button again.

Open Claude connector settings ↗

Manual setup in Claude

  1. Open Claude and go to Customize → Connectors.
  2. Select Add → Custom → Web or Add custom connector, depending on the interface.
  3. Name the connector MBRS Bio and paste the server URL above.
  4. Continue using Claude's detected authentication options. Choose Sign in now or Sign in when needed for account-based access, as available.
  5. Use Claude's recommended OAuth client setting if presented. Do not enter a personal MBRS password or a server API key in request headers.
  6. Approve the connector, complete secure MBRS sign-in, and confirm the requested access.
  7. In a Claude chat, select + → Connectors and enable MBRS Bio for that conversation.

Team and Enterprise organizations may require a Claude organization Owner to add the custom connector first. Organization members then connect using their own authorized MBRS identities.

MCP connection settings

Connector name
MBRS Bio
Connector type
Custom web connector (remote MCP)
Server URL
https://www.mbrsbio.com/api/mcp
Authentication
Secure sign-in with your approved MBRS account
OAuth client
Use Claude’s recommended published identity if offered and compatible
Request headers
None for the standard account sign-in flow

Connection settings may vary as Claude updates its interface. The correct choice is the secure account-authentication flow detected for this server; never select unauthenticated access as a workaround for a failed sign-in.

Access and confidentiality

You can use one email address for Claude and another for your approved MBRS account. MBRS access is determined by the MBRS identity authenticated during the connection, not by your Claude email address.

Connecting does not automatically approve a new MBRS account, start a trial, or release private reports. Only content authorized for the authenticated account may be accessed. You can disconnect MBRS from Claude's connector settings.

Try it in Claude

“Using my MBRS connection, show which asset–indication portfolios I can access and summarize the available reports.”

Available tools, reports, submissions, and downloads depend on account approval and enabled capabilities.

Troubleshooting

The install link opened Claude but did not prefill the form.

Sign in to Claude, return to this page, and click Connect MBRS to Claude again. Alternatively, copy the server URL and add a custom web connector manually.

The connection succeeds, but I cannot access reports.

Confirm you signed in using an MBRS account that is approved for the requested reports. Access is not inferred from your Claude login email.

I can't add a custom connector to my organization.

Ask your Claude Team or Enterprise organization administrator to add the connector, then use your own MBRS account to connect.

Need help? [email protected]

REST API for approved organizations

Use the MBRS REST API for server-to-server portfolio and report retrieval. Approval is separate from dashboard and Claude MCP access. Reports must belong to your MBRS account and must be released for distribution. Your API integration cannot request access to another account's content.

GET
/api/v1/me — Check authorized scopes
GET
/api/v1/reports — List your released reports
GET
/api/v1/reports/{jobId} — Inspect one released report
GET
/api/v1/reports/{jobId}/zip — Download a released ZIP
GET
/api/v1/reports/{jobId}/files — List released ZIP files
GET
/api/v1/reports/{jobId}/files?name=… — Download an approved file from a ZIP

Base URL: https://www.mbrsbio.com. Send Authorization: Bearer YOUR_API_TOKEN over HTTPS. Generate a short-lived, revocable personal API token below after signing in and receiving independent API approval. Do not send your MBRS password to a REST endpoint.

curl -H "Authorization: Bearer $MBRS_API_TOKEN" https://www.mbrsbio.com/api/v1/reports

An additional reports:download approval is required for ZIP downloads and files:read for ZIP members. Individual-file retrieval supports bounded, standard released ZIPs; larger archives can be downloaded directly. Separately stored MCP-only companions require their own verified release mapping before REST access.

Manage REST API access

REST API access is approved separately from your MBRS dashboard and Claude connector. Sign in to your approved MBRS account and obtain additional API approval before creating a personal integration token. Tokens expire after 14 days and can be revoked at any time.

Checking your API access…