Overview
Ocean doesn’t need to be listed in a client’s marketplace, directory, or app store to work —
any client that speaks MCP over streamable HTTP can connect. This guide covers the
generic setup; see the per-client guides in the sidebar for a walkthrough tailored to a
specific tool.
For connection details, authentication, and the full tool catalog, see the
MCP Server Overview.
What you need
Generic configuration
Most clients use some variant of this shape — the key names differ (url, httpUrl,
serverUrl), but the fields are the same. Check your client’s docs for its exact schema.
If your client supports OAuth for remote servers, add the entry with no credential and let it
run the sign-in flow the first time it connects. If it doesn’t — or you need the allow/deny
write tools, which OAuth can’t reach — add an X-Api-Key header instead:
Don’t commit a real API key to a shared config file. Reference an environment variable
instead — "X-Api-Key": "${OCEAN_API_KEY}" — where your client supports it.
Verify the connection
Use the MCP inspector to check the
endpoint independently of any client:
In the inspector’s UI, select Streamable HTTP, enter
https://api.ocean.security/mcp, connect, and confirm Ocean’s tools appear under
Tools → List Tools.
Troubleshooting
See the overview troubleshooting — it covers
the same failure modes regardless of client.