Connect Claude on the web, Claude Desktop, or Cowork to your company brain as a custom connector, and add the Hyperspell plugins.
Claude connects to Hyperspell as a custom connector. You paste one URL, sign in with your Hyperspell account, and Claude can search and ask the brain in any conversation. The connection is yours alone: Claude sees exactly what you are allowed to see. If you would rather not sign in, you can connect with an API key instead.
This page covers Claude on the web, Claude Desktop, and Cowork. For Claude Code, the terminal agent, see MCP clients or the command line tool.
You need a Hyperspell account. If you were invited by a teammate, accept the invitation first.
On Claude Team and Enterprise plans the setup has two parts, described below.
Copy your MCP URL from the dashboard under Settings, Connect Agents, Claude. For most organizations it is https://api.hyperspell.com/mcp, and accounts in the EU region use https://api.eu.hyperspell.com/mcp. Organizations on a dedicated Hyperspell instance have their own URL, which is why copying it from the dashboard is the safe choice.
In claude.ai or Claude Desktop, open Settings, then Connectors. Scroll to the bottom and click Add custom connector.
The Connectors page in Claude settings
2
Add Hyperspell
Give the connector a name, such as Hyperspell, paste the MCP URL, and click Add.
Adding the Hyperspell connector
3
Sign in and approve
Claude opens a Hyperspell sign-in page. Sign in with your Hyperspell account and approve the connection. You are returned to Claude, and Hyperspell appears in your list of connectors.
On Claude Team and Enterprise plans, connectors are added at the workspace level first and then connected by each person.
A workspace owner opens Organization settings, then Connectors, and clicks Add, then Custom, then Web. They enter the connector name and the MCP URL. No sign-in happens at this step. That is expected.
Each member then opens Customize, then Connectors, finds the Hyperspell connector, and clicks Connect. They sign in with their own Hyperspell account.
The second step matters. The connector is shared across the workspace, but each person’s connection is their own, so everyone sees only what they are allowed to see.
Claude can also authenticate with a Hyperspell API key instead of signing in. The connector then acts as the key, not as you. With a Company key, Claude sees only what is shared with the whole company and none of anyone’s personal data. See Permissions for what each audience can read.
1
Create an API key
In the Hyperspell dashboard, open Settings, then Connect Agents, and create an API key. Choose the audience Company. Copy the key: it starts with hs2- and is shown only once.
2
Check for an existing Hyperspell connector
In Claude, open Settings, then Connectors. On Team and Enterprise plans, a workspace owner opens Organization settings, then Connectors, instead. Claude allows only one connector per URL and cannot switch an existing connector from sign-in to an API key, so if a Hyperspell connector is already there, you have to delete it before adding the key version.
Deleting a connector disconnects everyone who signed in through it, and on Team and Enterprise plans that is the whole workspace. If people should keep their own Hyperspell access next to the company key, add their sign-in connector back at the /personal URL, as described in Company connector plus personal sign-in. Each person then connects and signs in again once.
3
Add the connector
Click Add custom connector, paste the MCP URL you copied from the dashboard under Settings, Connect Agents, and click Continue. For most organizations it is https://api.hyperspell.com/mcp, and accounts in the EU region use https://api.eu.hyperspell.com/mcp. Organizations on a dedicated Hyperspell instance must use the URL from the dashboard, because the shared endpoints do not know them.
4
Choose No sign-in and add the key
Select No sign-in. Under Request headers, click Add header, choose authorization in the left dropdown, and enter Bearer followed by a space and your key on the right, for example Bearer hs2-1234-.... The value is sent exactly as entered, so do not leave out Bearer.
The authorization header with a Hyperspell API key
5
Connect
Click Connect. Hyperspell appears in your list of connectors.
Anyone who can use this connector reaches the brain with the key’s access, so treat the key like a password. To cut off access, revoke the key in the dashboard under Settings, Connect Agents, API Keys.
On Team and Enterprise plans an owner can add Hyperspell once for the whole workspace with a Company key, so nobody needs a Hyperspell account to ask the shared brain. Claude allows only one connector per URL, though, so a member who also wants their own data in scope cannot add the same URL a second time and sign in.Hyperspell serves the same server under a second URL for exactly this: add /personal to your MCP URL, for example https://api.hyperspell.com/mcp/personal (https://api.eu.hyperspell.com/mcp/personal in the EU region).
The workspace owner adds the company connector with the plain MCP URL, No sign-in, and the Company key in the authorization header, as described above.
The workspace owner adds a second connector, named for example Hyperspell (personal), with the /personal URL, the same way as in Team and Enterprise plans: Organization settings, then Connectors, then Add, then Custom, then Web. They leave sign-in on. Members cannot add custom connectors themselves on these plans, so this step is the owner’s.
Each member who wants their own data opens Customize, then Connectors, finds the personal connector, clicks Connect, and signs in with their own Hyperspell account.
Every member sees both connectors in their list. Members who never connect the personal one keep using only the company connector.The personal URL only accepts sign-in. An API key pasted there is refused with a message pointing back at the plain URL, so a company key cannot end up in a connector labeled personal.
Enable one Hyperspell connector per conversation, not both. They offer the same tools with different scope, so with both on Claude may call each one and get answers that disagree. Use the company connector for shared questions and the personal one when your own email, calendar, or notes matter.
The connector gives Claude Hyperspell’s tools. Hyperspell also publishes two optional plugins that build on it:
Hyperspell Activity (hyperspell-activity) records what each Cowork or Claude Code session did. After a turn that did real work, it writes a short entry into the brain: what was done, what was decided, and what is next. Each session is one entry, revised as the session goes on, so your team can see what people and their agents worked on without anyone writing it up.
Hyperspell Brain (hyperspell-brain) is a skill that helps Claude answer questions about your organization, such as its people, projects, decisions, and priorities, from the brain.
The Hyperspell plugins are not in Claude’s plugin directory yet, so searching for Hyperspell under Customize, then Plugins, will not find them. For now, install them from Hyperspell’s own plugin marketplace, github.com/hyperspell/claude-plugins, or from the download below.
In Claude Desktop, open Customize, then Plugins, and click Add marketplace. Enter hyperspell/claude-plugins.
2
Install the plugins
Install Hyperspell Activity, Hyperspell Brain, or both.
3
Start a new session
Plugins load when a session starts, so open a new Cowork session. The first time Hyperspell Activity writes an entry, Claude asks once for permission to use the connector’s log_activity tool. Allow it, or the plugin pauses.
On Claude Team and Enterprise plans, an organization owner can install Hyperspell Activity once for everyone. Download the plugin file above, open Organization settings, then Plugins & skills, upload it, and set it to Installed by default or Required. Every member’s Cowork sessions then have it, with no step for each person. Each member still needs the Hyperspell connector connected.
suggest (the default): the entry stays yours, and your Hyperspell inbox asks whether to share it with the company.
shared: the entry is shared with the company at once, where your workspace allows direct sharing. Otherwise it falls back to suggest.
personal: the entry stays yours, and you are never asked.
If the connector uses a company API key instead of your own sign-in, every entry belongs to the company.In a session, /hyperspell-activity status shows whether capture is on, which connector it writes through, and how many entries it has written. /hyperspell-activity pause and resume turn it off and on, and /hyperspell-activity now writes the entry immediately.
Start a new conversation and make sure the Hyperspell connector is enabled. Claude shows connected tools in the menu below the message box, and you can toggle them per conversation.Then ask questions the way you would ask a colleague:
“What did we decide about the pricing page in the last planning meeting?”
“Who at Acme have we spoken to, and what did they ask for?”
“Summarize what is in the brain about the mobile app launch.”
Claude decides when to call Hyperspell. For a factual question it usually asks the brain directly and returns an answer with citations. For a broader task it may search first and read a few documents. You can also be explicit: “search Hyperspell for…” or “remember this in Hyperspell” both work.
Claude does not call Hyperspell. Check that the connector is enabled for the current conversation. Connectors can be turned off per chat, and a new chat sometimes starts with them off.The sign-in page does not appear, or the connection fails. On Team and Enterprise plans, confirm the workspace owner has added the connector first. If you are in the EU region, make sure you used the EU URL. If it still fails, contact us.Answers are missing things I know are in a tool. Check in the dashboard that the tool is connected and has finished its first sync. Also remember that Claude sees only what you can see: a colleague’s personal integration is not visible to you unless a sharing rule applies.I want to disconnect. In Claude, open Settings, then Connectors, and remove Hyperspell. In the Hyperspell dashboard, your personal API keys and connected agents are listed under Settings, Connect Agents.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.
