Connect your AI
How it works
Every app connects to the same address, and they all read and write the same brain. The first time an app connects, a SuperLoom sign-in page opens in your browser; approve it once and that app stays connected.
https://superloom.io/mcp
Sign-in uses OAuth with automatic registration, so there is no key or password to paste into any app. Some apps go further than the connector: the Claude Code plugin and the Gemini CLI extension also load your briefing when a session starts and offer to save what you learned when you wrap up.
| App | How to add it | Extras |
|---|---|---|
| Claude (web, desktop, mobile) | Custom connector | Personal preferences for always-on memory |
| ChatGPT | Custom MCP server | Custom instructions |
| Claude Code | Plugin, or one command | Session-start briefing, wrap-up review, slash commands |
| Cursor | One-click button | Rule file |
| VS Code (Copilot) | One-click button | Copilot instructions file |
| Codex | One command | AGENTS.md |
| Gemini CLI | Extension, or one command | Context file, wrap-up review, slash commands |
| Windsurf | Config file | Rule file |
| Goose | One-click link | .goosehints |
| Zed | Settings | Rules Library |
| Grok | Custom connector | |
| Vibe | Custom MCP connector (Mistral Studio) | |
| Perplexity | Custom connector (paid plans) | |
| Raycast | Install MCP Server (Pro) | |
| Cline and Roo Code | Config file | |
| Anything else | Remote MCP URL, or a local bridge |
Claude
Works on the web, in the Claude desktop app, and on mobile: a connector you add once on claude.ai shows up everywhere you sign in to Claude.
- Open Settings › Customize › Connectors › Add (+) › Add custom connector.
- Name it SuperLoom and paste the connector URL above.
- Select Continue › Add (OAuth and registration are detected automatically), then Connect, and approve the SuperLoom sign-in.
- Each tool asks for approval the first time. Set SuperLoom's read-only tools to "Always allow" to cut down on prompts.
On a Team or Enterprise plan, an owner adds the connector under Organization settings › Connectors and each member selects Connect. The free plan allows one custom connector.
Claude desktop app: use the same connector; you don't need to edit claude_desktop_config.json. That file and desktop extension bundles are for servers that run on your own computer, and SuperLoom runs on the web.
ChatGPT
ChatGPT calls these plugins (older screens say apps or connectors).
- Open Settings › Plugins (Integrations) › Browse directory › Add › Create custom MCP server.
- Paste the connector URL above as the server URL.
- Set Authentication to OAuth and confirm.
- Approve the SuperLoom consent screen.
Claude Code
The SuperLoom plugin is the best way in. Besides the connector it adds a start-of-session briefing, a reminder to review what to save when you wrap up, and slash commands.
/plugin marketplace add SuperLoom-io/plugins
/plugin install superloom@superloom
Then run /mcp, pick superloom, and approve the sign-in in your browser. The plugin's source is public at github.com/SuperLoom-io/plugins.
| Command | What it does |
|---|---|
/superloom:onboard | Runs SuperLoom onboarding, one step at a time. |
/superloom:brief | Your daily brief: today's meetings and open items. |
/superloom:review | Reviews what to save from this session and saves only what you approve. |
/superloom:handoff | Saves where you left off, so the next session picks up from there. |
/superloom:skills | Lists your skills, or runs one by name. |
/superloom:status | Your setup status and the next step. |
/superloom:build-skill | Builds a custom skill from a task you repeat. |
/superloom:profile | Shows what SuperLoom knows about you, to correct or remove. |
The plugin's hooks never send anything anywhere: they only add instructions to the session. Turn them down with environment variables: SUPERLOOM_BRIEFING=lazy loads the briefing only when a question needs it, SUPERLOOM_BRIEFING=off skips it, and SUPERLOOM_REVIEW=off stops the wrap-up reminder.
Connector only, without the plugin:
claude mcp add --transport http --scope user superloom https://superloom.io/mcp
If you added the connector this way before, remove it once you install the plugin (claude mcp remove superloom) so the tools aren't listed twice.
Cursor
Or add it by hand to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):
{
"mcpServers": {
"superloom": { "url": "https://superloom.io/mcp" }
}
}
Open Cursor Settings › MCP and select Connect next to superloom to sign in. For always-on memory, save the always-on snippet as a rule: paste it into Cursor Settings › Rules › User Rules, or save it as .cursor/rules/superloom.mdc with this header:
---
description: SuperLoom personal knowledge brain (MCP), always on
alwaysApply: true
---
VS Code (GitHub Copilot)
Install in VS Code Install in VS Code Insiders
Or run MCP: Add Server from the Command Palette, choose HTTP, and paste the connector URL. For one project, put this in .vscode/mcp.json:
{
"servers": {
"superloom": { "type": "http", "url": "https://superloom.io/mcp" }
}
}
Approve the sign-in when VS Code asks, then use SuperLoom from Copilot Chat in Agent mode. For always-on memory, add the always-on snippet to .github/copilot-instructions.md or AGENTS.md in your project.
Codex
For the Codex CLI and the Codex IDE extension, which share one config:
codex mcp add superloom --url https://superloom.io/mcp
codex mcp login superloom
Or add it to ~/.codex/config.toml yourself, then run the login command above:
[mcp_servers.superloom]
url = "https://superloom.io/mcp"
For always-on memory, add the always-on snippet to ~/.codex/AGENTS.md (every project) or a project's own AGENTS.md.
Gemini CLI
The SuperLoom extension adds the connector, a context file that turns on always-on memory, a wrap-up reminder to review what to save, and /superloom: commands (brief, review, handoff, skills, onboard, status):
gemini extensions install https://github.com/SuperLoom-io/plugins
Then run /mcp auth superloom inside Gemini CLI and approve the sign-in. Connector only:
gemini mcp add --transport http --scope user superloom https://superloom.io/mcp
The Gemini app (gemini.google.com) has no setting for adding your own connector on most plans yet. Where your plan has custom apps, add the connector URL there.
Windsurf
Add superloom to Windsurf's MCP config, which you can open from the MCP servers panel in Cascade (View raw config). The file is mcp_config.json, in ~/.codeium/windsurf/ on older versions and ~/.config/devin/ on newer ones:
{
"mcpServers": {
"superloom": { "serverUrl": "https://superloom.io/mcp" }
}
}
Refresh the MCP servers list and sign in when asked. For always-on memory, paste the always-on snippet into your global rules, or save it as .windsurf/rules/superloom.md starting with trigger: always_on in a front matter block.
Goose
Or add it under extensions in ~/.config/goose/config.yaml:
extensions:
superloom:
name: SuperLoom
type: streamable_http
uri: https://superloom.io/mcp
enabled: true
timeout: 300
Goose opens the sign-in in your browser the first time it uses SuperLoom. For always-on memory, add the always-on snippet to ~/.config/goose/.goosehints.
Zed
Open Settings › AI › MCP Servers › Add Server › Add Remote Server, or add this to your Zed settings file:
{
"context_servers": {
"superloom": { "url": "https://superloom.io/mcp" }
}
}
Zed runs the sign-in when it first connects. For always-on memory, add the always-on snippet to the Rules Library as a default rule.
Grok
- Open grok.com/connectors and select New Connector › Custom.
- Paste the connector URL and complete the sign-in when Grok asks.
On Grok Business and Enterprise, an admin adds connectors for the team.
Vibe
Mistral renamed Le Chat to Vibe. Custom MCP connectors are added in Mistral Studio, not Vibe itself:
- Open console.mistral.ai (Mistral Studio) and sign in.
- Add a custom MCP connector, name it
superloom(no spaces), and paste the connector URL. - Open Vibe and turn it on under Admin › Connectors.
On a shared workspace, only an admin can add connectors.
Perplexity
Custom connectors are on Perplexity's paid plans. Open Settings › Connectors › Add custom connector, paste the connector URL, choose OAuth and Streamable HTTP, and leave the client ID and secret empty: SuperLoom registers Perplexity automatically.
Raycast
MCP servers are a Raycast Pro feature. Run the Install MCP Server command, choose HTTP, paste the connector URL, and set OAuth to Dynamic. Sign in when Raycast asks, then mention @superloom in Raycast AI.
Cline and Roo Code
Open the MCP Servers panel, choose to edit the configuration, and add superloom. In Cline the type is streamableHttp; in Roo Code it is streamable-http:
{
"mcpServers": {
"superloom": { "type": "streamableHttp", "url": "https://superloom.io/mcp" }
}
}
If the app doesn't open a SuperLoom sign-in when it connects, use the local bridge below instead.
Anything else
Any app that takes a remote MCP connector with OAuth works the same way: paste the connector URL and approve the sign-in. For an app that only runs local MCP servers, the open-source mcp-remote bridge (it needs Node.js) handles the sign-in for it. Use this as the server entry:
{
"mcpServers": {
"superloom": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://superloom.io/mcp"]
}
}
}
Always-on memory
The connector lets your AI reach SuperLoom; the always-on snippet tells it to use SuperLoom in every chat without being asked. Your AI gives you this snippet during onboarding, and the Setup page in the SuperLoom web app has a copy button for it. Paste it wherever your app keeps standing instructions:
SuperLoom (MCP): start every chat with superloom_context, then superloom_status if setup isn't finished. Before answering about my people, companies, projects, meetings, or commitments, search first. Near a stopping point, offer a review (Remember these? / Add to your todos?) and save only what I approve, in one superloom_save batch. With spoonfeed on, go one item at a time with numbered choices. Coach me: suggest a skill or connection; if I sound frustrated or a tool would fix it, draft a superloom_feedback and ask before sending, at most once per chat. Skip small talk, secrets, credentials, and financial details. Never save health information (conditions, symptoms, medications, diagnoses, or an appointment's medical reason): save only the non-health part, e.g. "dentist appointment Tuesday" becomes "appointment Tuesday".
| App | Where the snippet goes |
|---|---|
| Claude | Settings › Capabilities › Personal preferences (or a Project's instructions) |
| ChatGPT | Settings › Personalization › Custom instructions |
| Claude Code | The plugin does this for you. Without it: ~/.claude/CLAUDE.md |
| Cursor | Settings › Rules › User Rules, or .cursor/rules/superloom.mdc |
| VS Code | .github/copilot-instructions.md or AGENTS.md |
| Codex | ~/.codex/AGENTS.md |
| Gemini CLI | The extension does this for you. Without it: ~/.gemini/GEMINI.md |
| Windsurf | Global rules, or .windsurf/rules/superloom.md |
| Goose | ~/.config/goose/.goosehints |
| Zed | Rules Library, as a default rule |
| Other apps | Their custom or standing instructions setting |
Troubleshooting
- The sign-in page never opened. Most apps sign in on the first tool call. Look for a Connect, Authenticate, or Sign in action next to SuperLoom in the app's MCP settings.
- "Not connected yet" on the Setup page. It updates after your AI makes its first SuperLoom call. Ask it "what's my SuperLoom setup status?"
- Disconnecting an app. Remove the connector in the app. Support has the details.