CollabHub
Sign inGet started

Connect an AI client

CollabHub speaks MCP (Model Context Protocol), so the AI tools you already use — Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code — can work with your lab directly: search your workspaces, read your notebooks and datasets, log observations, and upload results, all under your own permissions.

Connect in two minutes

  1. Sign in and open Settings → Connections. The Connect an AI client panel shows the exact, copy-paste setup for each client.
  2. Pick your client and follow its snippet. They all point at the same remote server: https://mcp.collabhub.ai/mcp. Claude Desktop adds it as a custom connector under Settings → Connectors, Claude Code is one terminal command, and Cursor and VS Code take a small mcp.json entry. ChatGPT connects the same way if your ChatGPT plan includes custom connectors.
  3. The first time your client reaches CollabHub, your browser opens a one-time OAuth sign-in. No token to copy, no secret in your config file.
  4. Review the consent screen: it names the app and the access it is asking for. Nothing is shared until you approve.

That’s it — ask your client to search your workspaces to confirm the connection.

What a connected client can do

  • Search across your workspaces, list their datasets, and query the knowledge graph.
  • Read notebook entries, datasets, protocols, and experiments. Entries arrive as clean Markdown — rich text, tables, code, and equations included — so models work with your real records, not screenshots.
  • Look up file details (name, type, size, scan status). File contents stay behind the app’s own download checks and are never streamed to a client.
  • Browse and read items shared to the public library.
  • Log experiment observations in batches of up to 100 in a single call.
  • Upload files and datasets into a workspace.

Every action runs as you: a client can never see or do more than your own role in each workspace permits, and every call is recorded in the audit trail.

Consent, control, and revoke

  • Consent first. Access only exists after you approve it on the consent screen, and only with the access listed there.
  • See every connection. Settings → Connections lists each connected app with what you granted and when.
  • Revoke instantly. One click severs an app — every credential it holds stops working immediately.

Advanced: tokens and self-hosting

Power users can mint personal access tokens on the same Connections page — each with its own scopes, optional expiry, and an optional allowlist limiting it to specific workspaces. The token is shown once, stored only as a hash, and can be revoked at any time. Operators who self-host CollabHub can run the MCP server locally over stdio; the Connections page includes that setup too, clearly marked as operator-only.