Connect Claude to your workspace

You can connect an external Claude (Claude Desktop, claude.ai, or Claude Code on your laptop) directly to your SupaNet workspace. This lets you use Claude's native tools and your own environment while sending the results — artifacts, notes, files, tasks — directly into your team's workspace.

Why you'd do this

• Create and share from outside the app — draft an artifact in Claude Desktop and send it to the workspace.
• Automate SupaNet tasks — a script or Claude Code session can push documents, notes, and files into SupaNet with a single command.
• Integrate your own tools — use Claude with Playwright, execute code, fetch external data, then file the results into collections.

Getting connected

1. Go to Settings → Connect Claude in your SupaNet workspace.
2. There are two ways to connect; the recommended method is the easiest:

Option 1: OAuth custom connector (recommended)

Works in Claude Desktop and claude.ai. This method is the simplest — no tokens to copy.

1. In Claude, open Settings → Connectors → Add custom connector.
2. Copy the workspace MCP URL from Settings → Connect Claude and paste it.
3. Leave OAuth Client ID and OAuth Client Secret empty — Claude will discover them automatically.
4. Claude opens a sign-in page. Log in with your workspace email and password.
5. Review and approve the connection. Done — tools appear immediately.

Note: If you haven't set a password yet (you use magic links), go to Settings → Profile and set one first.

Option 2: Personal token (Claude Code or fallback)

Best for Claude Code (the CLI), or if you prefer not to use OAuth.

1. Go to Settings → Connect Claude and generate a New connection token.

2. Follow the instructions for your setup:

   • Claude Code: Copy the command and run it in your terminal (anywhere — --scope user makes it available in every project).

     claude mcp add --scope user --transport http supanet <url> --header "Authorization: Bearer <token>"

     Then start claude and run /mcp — you should see supanet connected.

   • Claude Desktop: Open Settings → Developer → Edit Config and add the provided JSON block to the mcpServers section in your claude_desktop_config.json. The token is stored securely in an environment variable. Restart Claude Desktop and check the MCP icon (🔌) — you should see supanet connected.

Each connection uses a per-user token — your workspace is protected, and everything you push runs as you. Treat tokens like passwords; revoke them in Settings if they leak.

What you can do

Once connected, the supanet MCP server exposes tools to build and manage your workspace. These are the same tools that the internal chat assistant can use:

• Create & edit artifacts — save markdown, code, HTML, or plain text. Returns a shareable link.
• Push files — persist images, PDFs, and other output you generate. Get back a signed URL.
• Manage to-dos — create tasks, mark them done, set due dates, file them into collections.
• Save links — paste a URL and metadata (title, description, preview) are fetched automatically.
• Add notes — push transcripts, meeting notes, or research into the knowledge base.
• Query & edit tables — work with real Postgres data tables from your local environment.
• Build automation — create agents, tools, webhooks, skills, and scheduled runs. Admins can create always-on prompts and custom HTTP tools.

The workspace re-enforces access the same way it does for in-app users: you can only work with content you own or that's shared with the team. Admin-only actions (like creating always-on prompts or HTTP tools) require admin privileges in both the external Claude and the internal assistant.

A quick example

In Claude Code, once connected:

@artifact - create me a clean HTML dashboard showing revenue trends

Claude will use create_artifact to save the dashboard directly into your SupaNet workspace and return the share link.

Or pull data from a table, manipulate it outside, and push the results back:

@artifact - query the "leads" table, sort by close probability, save the top 10 to a file

Where to learn the details

Settings → Connect Claude also gives you access to a comprehensive SupaNet workspace skill. If you're using Claude Code or Claude Desktop, grab that skill — it's a full reference of all the tools, with patterns for filing into collections, searching the knowledge base, and more.

For the MCP server architecture, see the Building on SupaNet docs.

Not using Claude? Other ways in

MCP via OAuth or personal token is the primary way to connect external Claudes, but SupaNet is reachable from anywhere:

• From the terminal or a script: use the supanet CLI to call tools, manage to-dos and artifacts, and chain operations together. Works from a shell, cron job, or any environment that can run Node.
• Teaching an agent: install supanet-skills into Claude Code, pi, or Codex so the agent learns the workspace conventions without guessing.

See CLI & Skills for installation and examples.