OceanirDocs
MCP

MCP

Authentication and access

Oceanir accepts OAuth bearer tokens and scoped agent tokens for MCP tool calls. These credentials are separate from REST API keys.

Access requirements

Tool calls require approved Enterprise integration access. The server allows discovery methods such as initialize and tools/list without authentication, so a visible tool list does not confirm that an account can run analyses.

For organizational onboarding, follow Enterprise setup.

Connect with OAuth

  1. Add https://mcp.oceanir.ai to your MCP client.
  2. Let the client discover the server’s authentication settings.
  3. Sign in to the Oceanir account approved for your integration.
  4. Review the permissions on the consent screen and approve only the access you intend to grant.
  5. Return to the client and check your credit balance.

Your client manages the OAuth token. Never paste it into a prompt or share it in a support message.

Connect with an agent token

Approved Enterprise accounts can create a scoped token in Platform → Agent access. Choose the permitted tools, maximum analysis depth, and expiration date.

The token is shown once. Store it in your client’s private credential configuration and send it as a bearer header:

Authorization: Bearer YOUR_OCEANIR_AGENT_TOKEN

For Codex, keep the secret in an environment variable available to the client process and reference its name:

[mcp_servers.oceanir]
url = "https://mcp.oceanir.ai"
bearer_token_env_var = "OCEANIR_AGENT_TOKEN"
tool_timeout_sec = 180

Use either this token configuration or OAuth. Do not put the token value in a prompt, repository, or shared configuration. A REST key or browser session cookie cannot be used here.

Agent tokens work only with MCP and can be revoked from Agent access. They currently use personal account billing; organization workspaces do not issue them.

Resolve access errors

  • Missing or expired token: reconnect through OAuth or replace the expired agent token.
  • Access denied: confirm the signed-in account, approved integration access, and token permissions.
  • Depth not allowed: choose a depth permitted by the token, or ask the token owner to review its scope.

For the available operations, see the tool reference.