Connect an AI agent to Surfspace

Which workspace

Each workspace has its own MCP address. Sign in and this page rewrites every command below for the workspace you pick. Signed out, it shows the shared address — sign-in then asks which workspace to connect:

Before you start

• A Surfspace account — create one free.
• Free workspaces connect read-only: your agent can search and read but not change anything. Read-write tools (creating docs, updating tasks) need a workspace on a paid plan.
• A connection is scoped to one workspace — the one its address names. Everything the agent reads and writes stays inside it. To reach another workspace, add a second connection with that workspace's address.

Claude on the web & Claude Desktop

1. Open Settings → Connectors → Add custom connector.
2. Paste this server URL:

3. Click Add, then Connect. A Surfspace sign-in window opens — sign in and approve the permissions for the workspace the address names.
4. That's it. Ask a question about your workspace to confirm it's live.

Claude Code

One command:

The OAuth sign-in runs in your browser on first use. Prefer plugins? Our plugin marketplace bundles the connector with Surfspace skills for Claude Code.

Codex

Add the server, then sign in:

Or write it into your Codex config.toml by hand:

Cursor & VS Code

One click each — the link hands the editor a server named surfspace pointed at the address above.

• Add to Cursor
• Install in VS Code

Other MCP clients & API keys

Any MCP client that speaks Streamable HTTP with OAuth can use the same URL. For clients that take a bearer token instead, mint a scoped API key in Settings → Connected agents and send it as Authorization: Bearer sk_live_…. Keys are minted per workspace with exactly the scopes you choose.

Try these prompts

"Search my Surfspace workspace for our onboarding checklist and summarize it."

"Create a doc in Surfspace called 'Q3 launch plan' with an outline based on this conversation."

"What tasks are still in the build stage? Move TASK-42 to verify and add a comment on what changed."

"Read the README from my app's repo in Surfspace and suggest improvements."

What your agent can and can't do

The tools it sees are filtered by the permissions you approved — a read-only connection never even lists the write tools. Every tool is annotated so the agent knows which are read-only and which modify your workspace, and destructive operations (like rewriting a doc) are marked as such so clients can ask before running them. A connection can never reach a workspace other than the one its address names, and it can never see your Surfspace password.

Disconnecting

Remove the connector in your client's settings, or revoke its key in Surfspace under Settings → Connected agents — either one cuts off access immediately. What data flows to a connected app is covered in our privacy policy.

Support

Stuck? Email team@cloudsurf.com and a human will help.