Skip to main content
Use your client’s remote MCP server settings to add Surfer.

Before you start

You need your own Surfer account on a plan that includes MCP. Check that your client supports Streamable HTTP and OAuth, with automatic client registration or a URL it identifies itself by; its documentation should describe how to add a remote MCP server. A client that identifies itself by a URL must serve it from a host Surfer accepts, which the clients with their own setup guides do. What the server supports has the detail.

Connect Surfer

Use your client’s settings or configuration file to add the connection.
1

Add the server

Name the connection Surfer and enter these settings:Save the connection and use your client’s sign-in option if the browser does not open automatically.
2

Authorize Surfer

  1. Sign in with your Surfer account in the browser window that opens.
  2. Check the account next to Signed in as. If it is the wrong one, select Switch account and sign in with the right one.
  3. Choose the organization to connect, if you belong to more than one.
  4. Select Authorize, then return to your client.
To change the account of a connection you already made, see Disconnect or switch accounts.
3

Open a conversation

Start a new conversation with Surfer enabled. If your client has a tool picker, enable the Surfer tools there.

Verify the connection

Ask your assistant: Your assistant lists the workspaces you belong to in the organization you authorized. Each workspace has a name, type, location, and state. Choose an active workspace for content tasks. A list shorter than the one in the app is expected: over MCP, workspaces you are not a member of are not listed and cannot be reached. If the list is empty, ask an organization owner or admin to add you to a workspace. Continue with Skills for guided workflows or Use cases for example requests. If the request fails, see Troubleshooting. For the protocol and authentication requirements, see What the server supports.