ResearchOS

Connect your AI.

Give Claude Code, Claude Desktop, Claude.ai, ChatGPT, Codex or Cursor a read-only view of your own ResearchOS data — projects, experiments, lineage, credit statements. Nothing to copy by hand: sign in with your lab Google account and you're done.

Every one of these clients speaks OAuth 2.1 to https://nperseus.com/mcp — pick yours below, copy the one line it needs, and follow the two steps. No personal access token, no environment variable, nothing to paste into a config file by hand.

Claude Code

Paste this into Claude Code
Add the ResearchOS MCP server at https://nperseus.com/mcp (transport http) and install the plugin researchos from the marketplace Ayushkiller/researchos-plugins, then run its authentication.
  1. Open Claude Code and paste the prompt above.
  2. It registers the MCP server, installs the plugin from the researchos-plugins marketplace, and prompts you to authenticate.

What happens next: A browser tab opens the first time a ResearchOS tool is used — sign in with your lab Google account, approve access, done.

Tokens are visible and revocable any time at /workspace/connect-ai.

Claude Desktop

Connector URL
https://nperseus.com/mcp
  1. Settings → Connectors → Add custom connector.
  2. Paste the URL above, then click Connect.

What happens next: A browser tab opens — sign in with your lab Google account. Done.

Tokens are visible and revocable any time at /workspace/connect-ai.

Claude.ai

Connector URL
https://nperseus.com/mcp
  1. Settings → Connectors → Add custom connector (same flow as Claude Desktop, in your browser).
  2. Paste the URL above, then click Connect.

What happens next: A browser tab (or the same tab) prompts you to sign in with your lab Google account. Done.

Tokens are visible and revocable any time at /workspace/connect-ai.

ChatGPT

Connector URL
https://nperseus.com/mcp
  1. Settings → Connectors → Create.
  2. Paste the URL above, choose Authentication: OAuth, then Connect.

What happens next: A browser tab opens — sign in with your lab Google account. Done.

Custom connectors need a ChatGPT plan that supports them (Plus/Pro/Business/Enterprise) with Developer Mode or connectors enabled under Settings → Connectors → Advanced.

Tokens are visible and revocable any time at /workspace/connect-ai.

Codex

Run in your terminal
codex mcp add researchos --url https://nperseus.com/mcp
codex mcp login researchos
  1. Run both lines above in the terminal where you use the Codex CLI.
  2. The first line registers the server; the second starts sign-in.

What happens next: codex mcp login opens a browser tab — sign in with your lab Google account. Done.

Tokens are visible and revocable any time at /workspace/connect-ai.

Cursor

Connector URL
https://nperseus.com/mcp
  1. Settings → MCP → Add server.
  2. Paste the URL above, then sign in when prompted.

What happens next: A browser tab opens — sign in with your lab Google account. Done.

Tokens are visible and revocable any time at /workspace/connect-ai.

Clients without OAuth support

A ChatGPT Custom GPT's Action editor cannot run an interactive OAuth handshake for you the way a connector can. For that one case, create a personal access token instead at /workspace/connect-ai — it stays the fallback path for clients that only support a bearer token.

For admins: wiring a Custom GPT Action to OAuth

A Custom GPT's Action editor can drive the same OAuth flow other clients use, once one confidential OAuth client is registered for it. Register it with a POST /oauth/register body of { "token_endpoint_auth_method": "client_secret_post", "redirect_uris": ["https://chat.openai.com/aip/<gpt-id>/oauth/callback"] } (the <gpt-id> redirect URI is a placeholder — ChatGPT shows the exact one once you start configuring OAuth on the Action). Then in the GPT's Action Authentication settings choose OAuth with Auth URL /oauth/authorize, Token URL /oauth/token, scope read, and PKCE optional (the server supports S256 either way). See mcp/README.md §6 for the full walkthrough.