Connect deterministic wet-lab tools to your AI workspace
SciTuu MCP exposes all 29 research-use-only web utilities plus authorized workspace, analysis, export and delivery operations over Streamable HTTP. OAuth scopes determine exactly which tools each client can see.
01
Configure a remote HTTP MCP client
Choose Add remote MCP server or Add HTTP connector in your AI client.
Set the server URL to https://scituu.com/api/mcp/v1.
Your client reads SciTuu protected-resource metadata, registers as a public OAuth client when needed, and opens the SciTuu sign-in page.
Sign in or register, review the requested scopes, and approve access. Access tokens expire automatically and refresh tokens rotate.
Client field names differ. Use a remote/HTTP MCP transport, not a local stdio command. The endpoint uses OAuth 2.1 authorization code + PKCE S256 and stateless JSON responses.
Use https://scituu.com/mcp/ only as this setup page. MCP clients should send JSON-RPC POST requests to https://scituu.com/api/mcp/v1; GET on that endpoint is for metadata. Do not configure an SSE transport.
If tools are missing in Codex, Claude or ChatGPT, reconnect and approve the scopes for that workflow instead of pasting a long-lived bearer token.
04 · CLIENT QUICK START
Connect in about three minutes
Add the endpoint, continue to SciTuu OAuth, sign in or register, review the requested scopes, and return to your client. The three-minute figure is a launch SLO and will be published only after real-user validation.
claude mcp add \
--transport http \
--scope user \
scituu \
https://scituu.com/api/mcp/v1
claude mcp get scituu
CHATGPT · MCP APPS UI
Rich review widgets, with JSON fallback
In ChatGPT workspaces that expose developer mode or custom MCP/App connections, add the production endpoint, complete SciTuu OAuth, and approve only the scopes your workflow needs. Supported hosts can render plate maps, protocol diffs, import mappings and secure approval checkpoints directly from MCP resources; other hosts still receive the complete structured result.
Approval remains a signed-in SciTuu browser action. No model-generated approved:true field can authorize an external write.
05 · EXAMPLE PROMPTS
Tell your agent what to do, not which internal tool to pick
Use SciTuu MCP to calculate a PCR master mix for 24 reactions, 20 µL each, with 10% overage.
Use SciTuu MCP to import this qPCR XLSX, preview the column mapping, run ΔΔCt analysis, generate an Experiment Packet, and export CSV plus RO-Crate.
Prepare a Benchling delivery preview for this Experiment Packet, but do not execute it until I approve it in SciTuu.
Troubleshooting
Common client errors
401 or invalid bearer: reconnect through OAuth and sign in again.
Missing tools: reconnect with the scopes for the workflow bundle you need.
Rich UI not shown: the host may not support MCP Apps UI yet; use the structured JSON result.
Approval blocked: open the SciTuu browser approval page because model-only approved:true is ignored.
Registered users
Website privacy mode vs. Remote MCP
Anonymous visitors can still use browser-local calculators on the website. Remote MCP is account-based so workspace files, packets, exports and approvals can be tied to the signed-in user and audited.
Calculator MCP 1.0
Stable input and output contracts
Every tool publishes inputSchema and outputSchema. Tool results use one structured envelope with data, normalized units, warnings, assumptions, provenance and stable error codes.
The 24 Calculator MCP operations are non-destructive and idempotent. PubChem is marked as an external read-only lookup. Lab profile changes are advertised as write operations only when profile:write is granted.
Invalid bearer credentials are rejected with 401 and are never downgraded to anonymous access or a browser session.