Windsurf

Windsurf uses a standard MCP JSON config at a Codeium-specific path.

File location

~/.codeium/windsurf/mcp_config.json

Create the file if it doesn’t exist.

Config

{
  "mcpServers": {
    "versuno": {
      "command": "npx",
      "args": ["-y", "versuno-mcp"],
      "env": {
        "VERSUNO_API_KEY": "uk_live_xxx"
      }
    }
  }
}

Remote (hosted HTTP)

To use Versuno’s hosted server instead of npx, point Windsurf at the URL with serverUrl and your key as a bearer token:

{
  "mcpServers": {
    "versuno": {
      "serverUrl": "https://mcp.versuno.ai/mcp",
      "headers": {
        "Authorization": "Bearer uk_live_xxx"
      }
    }
  }
}

The hosted server provides the read/query tools only — pull_asset and push_asset need local disk access, so use the npx config above for those.

Enabling the server

Open Windsurf settings, navigate to the MCP section, and click Refresh (or restart Windsurf). The versuno server should show as connected.

Using it

Open Cascade (Windsurf’s chat panel) and reference Versuno in your prompts:

“Search Versuno for prompt assets about onboarding and load the first three.”

Windsurf asks for confirmation before each tool call. Keep this on. See Security.

Troubleshooting

Windsurf surfaces MCP errors in its settings panel under MCP Servers. Click the server to see the stderr output. See Troubleshooting.

Getting Started

Clients

Tools

Reference

File location

Config

Remote (hosted HTTP)

Enabling the server

Using it

Troubleshooting

​File location

​Config

​Remote (hosted HTTP)

​Enabling the server

​Using it

​Troubleshooting

File location

Config

Remote (hosted HTTP)

Enabling the server

Using it

Troubleshooting