Does Codex support the Digitalocean MCP server?

Yes. Codex connects to the Digitalocean MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.

Do I need an API key to connect Digitalocean to Codex?

No. You sign in to Digitalocean once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.

Which Digitalocean tools can Codex use?

All 46 Digitalocean tools your team allows, such as Manage Node Pools, Get App, Manage Firewall. Admins can narrow that list per team.

Can I control which teammates use Digitalocean in Codex?

Yes. Role-based access control decides who can use Digitalocean and which of its tools appear in Codex, and every call is logged with the person's identity.

What if Codex doesn't show Digitalocean tools?

Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.

Connect Digitalocean to Codex (MCP setup guide)

Ask Codex to use the manage project resources tool in Digitalocean
Ask Codex to use the manage reserved ips tool in Digitalocean
Ask Codex to use the delete database cluster tool in Digitalocean
Ask Codex to use the list apps tool in Digitalocean
Ask Codex to use the list domains tool in Digitalocean

1. Enable Digitalocean in Metorial
In your Metorial portal, enable the Digitalocean MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
2. Add the server and sign in
The Codex CLI, IDE extension and ChatGPT desktop app share this config.
```
codex mcp add metorial --url <your-magic-mcp-url>
codex mcp login metorial
```
3. Check the connection
Type /mcp in Codex to see Metorial and its Digitalocean tools.

Once Digitalocean is enabled in Metorial, teammates sign in with SSO and get the same connection in Codex, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

Manage Node Pools: List, add, or remove node pools in a Kubernetes cluster.
Get App: Get detailed information about an App Platform application, including its full specification, deployment status, and URLs.
Manage Firewall: List, create, or delete cloud firewalls.
Deploy App: Trigger a new deployment for an App Platform application.
Get Account: Get your DigitalOcean account information including email, Droplet limit, billing status, and team details.
Manage Database Users: List, create, or delete users on a managed database cluster.
Manage Project: Create, update, or delete a project.
List Snapshots: List snapshots of Droplets and volumes.
Create Droplet: Create a new Droplet (virtual machine) in DigitalOcean.
Create Domain: Add a new domain to DigitalOcean DNS management.
List Kubernetes Clusters: List all managed Kubernetes clusters in your DigitalOcean account.
Droplet Action: Perform an action on a Droplet: **power_on**, **power_off**, **reboot**, **shutdown** (graceful), **resize**, **rebuild**, **rename**, or **snapshot**.
Manage Tags: List, create, delete tags, or tag/untag resources.
Delete Volume: Delete a block storage volume.
List Alert Policies: List all monitoring alert policies.
And 31 more on the Digitalocean MCP server page.

Limit which Digitalocean tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
Type /mcp in the composer to see the connected servers.
Override the approval behavior for a single Digitalocean tool with tools.<tool>.approval_mode.

Metorial is listed but tools are missing: Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.
Metorial times out at startup: Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.
Long tool calls fail after a minute: The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.

Frequently asked questions

Common questions about connecting Digitalocean to AI agents with Metorial.

Does Codex support the Digitalocean MCP server?
Yes. Codex connects to the Digitalocean MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.
Do I need an API key to connect Digitalocean to Codex?
No. You sign in to Digitalocean once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.
Which Digitalocean tools can Codex use?
All 46 Digitalocean tools your team allows, such as Manage Node Pools, Get App, Manage Firewall. Admins can narrow that list per team.
Can I control which teammates use Digitalocean in Codex?
Yes. Role-based access control decides who can use Digitalocean and which of its tools appear in Codex, and every call is logged with the person's identity.
What if Codex doesn't show Digitalocean tools?
Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.