MCP Integration
MCP lets you connect AI tools like ChatGPT, Claude, Cursor, VS Code, and others — directly to your Hyperdocs workspace. Once connected, those tools can read and interact with your workspace's documentation without any copy-pasting. Each workspace gets its own MCP connection with a unique Server URL that acts as the credential for that workspace.
How It Works
Connecting generates a Server URL scoped to the workspace you are currently in. You paste that URL into your AI tool of choice. The tool then communicates with Hyperdocs over the MCP protocol and can read and edit the workspace's docs directly. Switching to a different workspace in the admin shows that workspace's own connection — each workspace has one independent connection.
The Server URL contains an embedded token and grants access to the workspace, so it should be treated like a password. The URL field masks the token portion by default and only reveals it on request.
Access and Restrictions
MCP connections can only be created and revoked by the workspace owner. Invited members (Admins, Editors, and Viewers who were added to the workspace rather than being its creator) see a notice explaining that only the owner can manage MCP for this workspace. If you need MCP access as an invited member, ask the workspace owner to connect it.
Connecting Your Workspace
Open MCP
Go to MCP in the admin sidebar. If you do not see it, confirm you are the workspace owner.
Create the connection
Click Connect. Hyperdocs generates a unique Server URL for this workspace. The button shows Connecting… while the request is in flight.
Copy the Server URL
The connection card appears with a Server URL field. Click Copy to copy the full URL to your clipboard. The token portion is masked by default — click the reveal button to show it in full if you need to verify it.
Paste into your AI tool
Follow the setup steps for your specific tool in the Connect a tool section below the connection card. Each tool tab shows the exact steps for that client.
The Connection Card
Once a connection exists, the card shows the workspace name, a status badge, and the Server URL field. The status badge reads Ready until a tool has made its first request using the URL, then switches to Connected. The field below the badge also shows which tool last connected (for example, `openai-mcp/1.0.0`) once one has been used.
Field / Control | What it does |
|---|---|
Status badge — Ready | The connection exists but no tool has used the Server URL yet. |
Status badge — Connected | At least one tool has successfully called this workspace using the Server URL. |
Client name line | Shows the identifier of the last tool that connected, e.g. `openai-mcp/1.0.0`. Shows Not used yet until first use. |
Server URL field (masked) | Displays the host and masks the token with bullet characters. Safe to leave on screen. |
Reveal / Hide button | Toggles the token portion of the URL between masked and plain text. |
Copy button | Copies the full unmasked URL to the clipboard and briefly shows a checkmark to confirm. |
Disconnect button | Opens a confirmation dialog before revoking the connection. |
Connecting a Tool
The Connect a tool section below the connection card has a tab for each supported client. Select the tab for the tool you want to connect and follow the numbered steps shown. Every client uses the same Server URL — copy it once from the connection card and paste it wherever the steps ask for it.
ChatGPT
Open ChatGPT and click your profile icon → Settings.
Go to Plugins.
Click New plugin.
Name it Hyperdocs.
Paste the Server URL into the Server URL field.
Set Authentication to No Auth.
Check I understand and want to continue, then click Create.
Ask ChatGPT: `List my Hyperdocs documents`
Claude
Open Claude and go to Settings → Connectors.
Click Add custom connector.
Name it Hyperdocs.
Paste the Server URL into the Remote MCP server URL field.
Click Add, then enable Hyperdocs in the chat composer.
Ask Claude: `List my Hyperdocs documents`
Claude Code
Open a terminal in your project.
Run the command below, replacing `YOUR_SERVER_URL` with the URL from the connection card.
Start Claude Code and run `/mcp` to confirm Hyperdocs is connected.
Ask it: `List my Hyperdocs documents`
claude mcp add --transport http hyperdocs "YOUR_SERVER_URL"Cursor
Open Cursor → Settings → MCP → Add new global MCP server.
Add the entry below to `mcp.json`, replacing `YOUR_SERVER_URL` with the URL from the connection card, then save.
Reopen the MCP settings — Hyperdocs shows as connected.
Ask it: `List my Hyperdocs documents`
{
"mcpServers": {
"hyperdocs": {
"url": "YOUR_SERVER_URL"
}
}
}VS Code
Open the Command Palette and run MCP: Add Server.
Choose HTTP as the server type.
Paste the Server URL when prompted.
Name it `hyperdocs` and pick where to save it (workspace or user).
Open Copilot Chat in Agent mode — the Hyperdocs tools are listed.
Ask it: `List my Hyperdocs documents`
Codex
Add the entry below to `~/.codex/config.toml`, replacing `YOUR_SERVER_URL` with the URL from the connection card.
Restart Codex — the Hyperdocs tools are available in the session.
Ask it: `List my Hyperdocs documents`
[mcp_servers.hyperdocs]
url = "YOUR_SERVER_URL"Disconnecting
Click Disconnect on the connection card. A confirmation dialog appears with the warning: Every tool using this server URL stops working immediately, and the URL cannot be restored. Connecting again gives you a new one you'll need to configure again. Click Disconnect in the dialog to confirm, or close it to cancel.
After disconnecting, the card is replaced by the empty state and a new Connect button. The workspace's documentation is not affected — only the MCP credential is removed.
One Connection Per Workspace
Each workspace supports one active MCP connection at a time. The connection is scoped to the workspace you are currently viewing in the admin. If you manage multiple workspaces, use the workspace switcher in the top bar to move between them — each workspace's MCP screen shows only that workspace's own connection.