Optidata Cloud MCP server

1. Sign in to the Optidata Cloud console and open your account's API keys.
2. Create a key with a scope and an expiry that match what you need. This is the key the server uses to act on your account.
3. Copy it. It starts with ocs_.

The key's scopes decide which tools your client is offered. A key scoped to DNS is offered DNS tools only.

Every client talks to the same hosted endpoint. The repository ships one manifest per client, so the only thing you configure is the API key.

Claude Code

Add the marketplace and install the plugin:

/plugin marketplace add optidatacloud/ocs-mcp-plugin
/plugin install optidata-cloud@optidata

Claude Code then asks for your Optidata Cloud API key. Paste the ocs_ key. The field is hidden as you type and the key is kept in your system keychain, never in the chat and never in a file that syncs to git. Run /mcp to confirm the ocs server from the optidata-cloud plugin is connected.

Without the plugin, the same endpoint works as a plain MCP server. You get the tools but not the provisioning skill, which only the plugin carries:

claude mcp add --transport http ocs \
  https://console.optidata.com/api/v1/mcp \
  --header "x-api-key: ocs_..."

Codex

Codex connects to remote MCP servers with a URL and a header. In ~/.codex/config.toml:

[mcp_servers.optidata_cloud]
url = "https://console.optidata.com/api/v1/mcp"
http_headers = { "x-api-key" = "ocs_..." }

Not verified. The plugin repository marks this block as untested end to end. Confirm the key names, such as http_headers, against your Codex version's documentation.

Cursor

The repository ships a Cursor plugin manifest (.cursor-plugin/plugin.json) that points at the same server configuration. Cursor connects like any Streamable HTTP client: use the endpoint above and send your key in the x-api-key header.

Gemini CLI

The repository ships gemini-extension.json, which reads the key from the OCS_API_KEY environment variable. Export it before starting the CLI:

export OCS_API_KEY=ocs_...

The server block of that manifest, as published in the repository:

{
  "name": "optidata-cloud",
  "version": "1.0.1",
  "mcpServers": {
    "ocs": {
      "httpUrl": "https://console.optidata.com/api/v1/mcp",
      "headers": { "x-api-key": "$OCS_API_KEY" }
    }
  }
}

Other clients

Any client that speaks Streamable HTTP connects the same way: point it at the endpoint and send x-api-key. A bridge such as mcp-remote is only needed for a client that speaks stdio and nothing else.

claude.ai custom connectors are not verified. Whether claude.ai can attach a static header is unconfirmed, and the OAuth path a browser flow would need is not available yet.

Tools are derived from the live Optidata Cloud API contract, so a new API route becomes a tool without a plugin update. Resources are addressed by name, not by UUID.

Two helper tools: estimate_instance_cost quotes an instance without creating anything, and wait_for_instance_state waits for a new instance to reach a state such as Running. The default login user on Optidata Cloud VMs is ocs-user.

Not available through MCP: backups, monitoring and metrics, invoices, wallet and payments. Use the console for those. Object storage tools return metadata only, with no object content and no pre-signed URLs.

The Optidata Cloud API identifies locations by code. The code us-east-1 is Optidata's own Miami (US1) region, in Miami, Florida. It is not an AWS region and has no relation to AWS. Self-serve resources run in Miami (US1).

Clients should call location_list_locations first and pass a code it returned, never a code they invent or translate. The Object Storage location list is not the same as the compute region list.

These guarantees are enforced on the server, so they hold in every client.

• Nothing billable is created silently. A create that costs money first returns an itemized monthly price and waits for your explicit go-ahead.
• Destructive actions are two-step. Deleting, detaching, stopping or rebooting shows what is affected, then requires you to type the resource's exact name. Confirmation tokens are single-use and expire in about five minutes.
• Your key decides what is offered. The tool list is filtered by the key's scopes.
• Some operations are always off. Creating S3 access keys, exporting a certificate's private key, importing a certificate and exporting a DNS zone file cannot be enabled by any setting.
• Secrets stay out by default. Tools that would put a secret in the conversation, such as a VM's root password or a console URL, are controlled on the server and cannot be switched on from your side.
• Prompt-injection guard. Data returned by the API is fenced as untrusted, so text inside your own resources is never treated as an instruction.

If a create would exceed your quota, the server answers 402 with current usage and limits. The client should show you the extra cost and continue only after you approve it.

• 401: the key is missing, invalid, expired or revoked. In Claude Code, open /plugin, pick optidata-cloud and paste a valid ocs_ key. In other clients, check that the x-api-key header reaches the request.
• Server not listed in Claude Code: run /plugin manage and check that the plugin is enabled.
• Tools seem to be missing: call mcp_whoami. It reports the company, the key's scopes and the tiers enabled.
• An action fails with a valid key: the tool's error says why, such as a missing scope, a suspended account or quota, and what to do next.

Still stuck? Contact support, available 24/7/365 with human engineers.

• Machine-readable description: /.well-known/mcp.json.
• MCP Registry entry in the repository's server.json, under the name cloud.optidata/ocs-mcp-server.
• Release history: CHANGELOG.md. Version 1.0.0 moved the server from a local process into the hosted API on July 30, 2026.
• Product changes on the platform: Optidata Cloud changelog.