Before you start
You need your own Surfer account on a plan that includes MCP. Open VS Code with GitHub Copilot enabled. Your organization’s policy must allow MCP servers.Connect Surfer
1
Add the server configuration
Create If the file already contains servers, add
.vscode/mcp.json in your workspace and add:surfer inside the existing servers object.For a configuration available across workspaces, run MCP: Open User Configuration from the Command Palette and add the same entry there.2
Start the server
Run MCP: List Servers from the Command Palette, select
surfer, and start it. Review and accept VS Code’s trust prompt. VS Code opens your browser for the Surfer sign-in.3
Authorize Surfer
- Sign in with your Surfer account in the browser window that opens.
- Check the account next to Signed in as. If it is the wrong one, select Switch account and sign in with the right one.
- Choose the organization to connect, if you belong to more than one.
- Select Authorize, then return to your client.
4
Enable Surfer in chat
Open Chat in agent mode. Use the tools picker to enable the Surfer tools you want to use.
Verify the connection
Run MCP: List Servers and check thatsurfer is running. If some tools are missing from chat, check the client tool limit.
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.