Cline

Cline manages MCP servers from its MCP Servers panel, which writes to cline_mcp_settings.json. Click the MCP Servers icon, then Configure MCP Servers to edit the JSON directly. Use the hosted server with a header token, or the local stdio server for full read/write.

Hosted server (header token)

Add a remote server with the streamableHttp transport type. The value must be spelled streamableHttp (camelCase, no hyphen) — other spellings make Cline fall back to SSE and fail:

{
  "mcpServers": {
    "oceanum-datamesh": {
      "type": "streamableHttp",
      "url": "https://mcp.oceanum.io/datamesh",
      "headers": {
        "X-DATAMESH-TOKEN": "your-datamesh-token"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Replace your-datamesh-token with your Datamesh token.

The hosted server is read-only and returns query_data results inline (up to ~50 MB), so large results can’t come back in the conversation. To get large data, call export_query: on the hosted server it returns a time-limited download link to the full result, which you fetch out-of-band (e.g. with curl) — the link needs no token, so treat it like a password. The local server below instead writes export_query output to a file on your machine.

Local server (stdio)

For full read/write, and to have export_query write results straight to a file on your machine (NetCDF, Parquet or CSV) rather than return a download link, run the server locally:

{
  "mcpServers": {
    "oceanum-datamesh": {
      "command": "uvx",
      "args": ["oceanum-mcp", "datamesh"],
      "env": { "DATAMESH_TOKEN": "your-token-here" },
      "disabled": false,
      "autoApprove": []
    }
  }
}

This requires uv on your PATH.

Keep your token safe

Your Datamesh token grants access to all of your organisation’s permissioned datasources — including the ability to modify or delete them. Treat it as a secret, and prefer the hosted read-only server for exploratory use.