Cursor

Cursor reads ~/.cursor/mcp.json for every project, and .cursor/mcp.json for one. Add Marina to either:

{
	"mcpServers": {
		"marina": {
			"url": "https://mcp.marinahost.app/mcp"
		}
	}
}

Reopen Cursor and sign in when it asks. There is no token in that file, so it is safe to commit, and you can withdraw the access from Marina later.

Running it yourself instead

For an assistant confined to your own machine, or one holding a credential you minted:

{
	"mcpServers": {
		"marina": {
			"type": "stdio",
			"command": "marina",
			"args": ["mcp"],
			"env": {
				"MARINA_API_TOKEN": "<token>"
			}
		}
	}
}

Mint that token first, so Cursor is not holding your own credential:

marina tokens create cursor --preset agent --spend 200

Reopen Cursor. Marina’s tools appear in the agent’s tool list, filtered to what the credential allows.

Keeping the token out of the repo

The project file takes the token literally, so a committed .cursor/mcp.json leaks it. Two ways out: put the entry in ~/.cursor/mcp.json instead, or point at a file Git ignores:

{
	"mcpServers": {
		"marina": {
			"type": "stdio",
			"command": "marina",
			"args": ["mcp"],
			"envFile": "/absolute/path/to/.env"
		}
	}
}

Without a token

Leave env off and the server uses whatever marina login stored on that machine, which is your own account with all of your permissions. Fine while you are trying it, wrong for anything that runs unattended.

When it does not connect

Cursor starts marina as a subprocess and does not necessarily inherit your shell’s PATH. Run which marina and put the absolute path in command.