Skip to content

Devin

Devin (Cognition) reaches the Datamesh MCP server in two places: the cloud agent connects to remote MCP servers from its MCP Marketplace, and the Devin CLI (“Devin for Terminal”) runs a local server from a config file.

The cloud agent connects to remote MCP servers added through the MCP Marketplace in Settings.

  1. Open Settings → MCP Marketplace and choose Add your own MCP.
  2. Give it a name (for example Oceanum Datamesh), set Transport Type to HTTP, and add a short description.
  3. Set the Server URL to https://mcp.oceanum.io/datamesh.
  4. Choose an authentication method (see below), enable the server, and Devin will connect on first use.
  • If the dialog offers an API-key or token option, supply your Datamesh token: the hosted server accepts it as a bearer credential.
  • OAuth (“sign in”) is not yet available for Devin. The hosted sign-in flow currently allowlists only Anthropic’s Claude clients, so Devin’s OAuth cannot complete against the Datamesh server until its callback is registered on the Oceanum identity tenant. Contact Oceanum if you need this enabled.

The hosted server is read-only and returns query_data results inline (up to ~50 MB). For larger results, Devin can call export_query, which on the hosted server returns a time-limited download link to the full result — the link needs no token, so treat it like a password. The Devin CLI below instead writes export_query output to a file.

The Devin CLI adds MCP servers from .devin/config.local.json (gitignored, so your token stays out of version control). Run the Datamesh server locally over stdio for full read/write:

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

Replace your-token-here with your Datamesh token. This requires uv on your PATH. The local server gives full read/write and has export_query write results straight to a file on your machine. Remote MCP servers that use OAuth are added instead with devin mcp login <name>.

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.