Connect
Same endpoint as Supermemory MCP — there’s no separate Company Brain server to point at:sm_ skips OAuth entirely.
What changes isn’t the URL, it’s what shows up once you’re connected. If your account belongs to an org with Company Brain, you get more than your own project spaces — your employee memory, the private channels you’re in, and public channel memory all become available as workspaces, carrying your role and the exact same read/write access Slack already enforces.
Pick a workspace
Once connected, ask it what’s available — it returns every container tag you have access to: your employee memory, each private channel memory you belong to, and public channel memory. Select one to make it the active workspace for the session; everything after that scopes to it automatically. Example: from Claude Code, “what can I access in Acme’s Company Brain?” surfaces your options as a picker — your employee memory,#eng’s private channel memory if you’re in it, public channel memory. Pick one, and every search or save for the rest of the session happens inside it — the same as asking from that room in Slack.
Tools
Same graph, same guardrails
Nothing here is a side door. What you can reach follows the exact same permissions graph as Slack — an admin can restrict a member’s connection to specific container tags the same way they’d scope a Slack channel invite, and every read or write is checked against that before it runs.The permissions graph
What each container tag actually is, and who can read it.
Supermemory MCP
Base setup, auth, and personal project spaces on the same server.