Biomni MCP connector for AI agents

Biomni MCP tools for AI agents

CALL ANY TOOL

10 tools covering create, list.

biomnimcp_list_files

List files

List the input files already uploaded to a project. Returns the files a user added through the Biomni web app's project files panel (or earlier via upload_file) : the same files the agent can read during any task in that project. This is how you discover the file_id of an already-uploaded file: files are NOT attached to a task automatically, so pass the returned file_id values in the file_ids argument of start_new_task or send_message to attach them. Only input files are listed here : result files the agent produced are listed by list_result_files(task_id) instead.

Parameters

Name

Type

Required

Description

project_id

string

Required

The project whose files to list. Required.

limit

integer

Optional

Max files to return (1-100, default 50). When the result has has_more: true the project holds more files than were returned; raise limit to see them.

biomnimcp_send_message

Send message

biomnimcp_list_tasks

List tasks

biomnimcp_create_project

Create project

biomnimcp_list_projects

List projects

biomnimcp_upload_file

Upload file

biomnimcp_list_workspaces

List workspaces

biomnimcp_request_review

Request review

biomnimcp_list_result_files

List result files

biomnimcp_switch_workspace

Switch workspace

biomnimcp_start_new_task

Start new task

biomnimcp_wait_for_next_update

Wait for next update

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="biomnimcp")

mcp = MultiServerMCPClient({
    "biomnimcp": {
        "url": "https://mcp.scalekit.com/biomnimcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "biomnimcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/biomnimcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "biomnimcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/biomnimcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="biomnimcp")
# Connect to MCP at https://mcp.scalekit.com/biomnimcp
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Get started

Copy the prompt

Copied

Create a new Biomni project in the caller’s current workspace?

Copy the prompt

Copied

List the caller’s projects in the active workspace?

Advanced

Copy the prompt

Copied

Send a user message to an existing Biomni task and trigger AI agent execution?

Copy the prompt

Copied

Auto-create a Biomni task in a project and send the first message in a single call, triggering AI agent execution?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

Biomni MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Biomni MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Biomni MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Biomni MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

GTM and RevOps Teams

Competitive intelligence briefing agent

Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.

GTM and RevOps Teams

Outbound prospecting agent

Searches Apollo for prospects matching your ICP, scores and ranks them, drafts personalized outreach in Gmail, and logs every send to Google Sheets. Mail goes out as the rep, not from a shared inbox.

GTM and RevOps Teams

Deal intelligence agent

Pulls recent Gong calls, scores deal risk with an LLM, cross-references the record in Attio, and DMs each owner their at-risk deals in Slack. Every read is scoped to that rep's own access.

Support and Ops Teams

Support triage agent

Fetches new Zendesk tickets, classifies them by type and urgency, searches the Notion knowledge base for an answer, and routes what it cannot resolve to Slack. Every call runs on the support agent's own delegated OAuth.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Biomni as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Biomni OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Biomni?
Yes. Pass a tool name filter to listScopedTools so the analytics agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Biomni.

What happens when a user revokes Biomni access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Are biomedical analyses isolated per researcher?
Yes. Projects, tasks, and result files stay inside the authorizing user's Biomni workspace. Genomic data and analysis outputs never cross user boundaries.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit