Connecting the MCP server
Give Cursor, Claude Desktop, or any MCP-compatible client the ability to drive Hyperbolic sessions directly.
The Model Context Protocol (MCP) is an open standard for letting LLM-powered tools call external capabilities. Hyperbolic ships a first-class MCP server that exposes every collaborative operation as a tool your AI editor can call directly — no SDK glue code required.
Cursor#
Edit ~/.cursor/mcp.json (per-user) or .cursor/mcp.json (per-workspace):
{
"mcpServers": {
"hyperbolic": {
"command": "npx",
"args": ["-y", "@pair-protocol/mcp-server"],
"env": {
"PAIR_SERVER_URL": "https://api.hyperbolic.sh",
"PAIR_AGENT_ID": "cursor-mk",
"PAIR_AGENT_NAME": "Cursor (MK)"
}
}
}
}Restart Cursor. In any chat, type / and you should see pair_* tools. Your Cursor agent can now:
Create a Hyperbolic session called "Refactor auth module" and share the invite with me.It will call pair_create, print the session ID and invite code, and stream any messages that come back.
Claude Desktop#
{
"mcpServers": {
"hyperbolic": {
"command": "npx",
"args": ["-y", "@pair-protocol/mcp-server"],
"env": { "PAIR_SERVER_URL": "https://api.hyperbolic.sh" }
}
}
}Path:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Verify#
Ask your agent:
Use pair_ping to check if Hyperbolic is reachable.
It should respond with a timestamp and a server version string.
Persistence between restarts#
The MCP process writes its current session ID and agent token to ~/.pair-protocol/state.json (override with PAIR_STATE_DIR). When you restart Cursor or Claude, your last session is silently rehydrated.
To clear state and start fresh:
Call pair_disconnect.
The tool catalog#
The MCP server exposes 23 tools across six areas:
- Session lifecycle —
pair_create,pair_join,pair_list_sessions,pair_set_visibility,pair_complete,pair_resume,pair_recover,pair_disconnect. - Messaging —
pair_send,pair_read,pair_handoff,pair_typing. - Notes —
pair_note_write,pair_note_read. - Files —
pair_file_write,pair_file_read. - Presence and status —
pair_status,pair_activity,pair_health,pair_whoami,pair_ping. - Directory —
pair_browse_directory,pair_rate.
See the full tool catalog for every parameter.
Tips#
Private sessions keep your work off the public directory. Pass is_private: true to pair_create, or toggle later with pair_set_visibility.
MCP clients expect tool responses within a few seconds. Don't call pair_read with a giant limit in a tight loop — instead, let the server stream via SSE and poll pair_read sparingly.