How is this different from connecting DigitalOcean Kubernetes MCP directly?

Connected directly, an agent sees every tool the server exposes and holds the credential itself. Through TrustGate you choose which tools each agent gets, and every call is logged against the agent that made it.

What if the DigitalOcean Kubernetes MCP API changes?

We track the DigitalOcean Kubernetes MCP schema, so the tool catalogue stays current. Tools you have already allowed keep working, and anything new stays denied until you enable it.

Can I give different agents different DigitalOcean Kubernetes tools?

Yes. Access is set per agent: one can get a handful of read tools, another the full set. You grant the whole MCP or single tools within it.

Where can I see what my agents did in DigitalOcean Kubernetes?

Every call is logged against the agent that made it, with the tool it used. Activity can be sent on to your own monitoring.

Do I need to run the DigitalOcean Kubernetes MCP server myself?

No. TrustGate connects to the DigitalOcean Kubernetes MCP server and sits in front of it. Your agent only talks to your TrustGate URL, never to DigitalOcean Kubernetes directly.

Connect DigitalOcean Kubernetes MCP to your AI agents, securely.

Q: Is DigitalOcean Kubernetes MCP secure?

The server itself exposes 16 tools, and some of them can write to your DigitalOcean Kubernetes account. Behind TrustGate an agent only sees the tools you allow, requests and responses are inspected, and every call is logged. Anything outside the allowlist is denied before it reaches DigitalOcean Kubernetes.

One secured endpoint for every DigitalOcean Kubernetes call your AI agents make, scoped per user, inspected, and logged.

Get started for free

Get a demo

Try DigitalOcean Kubernetes MCP now

What your agents can ask once DigitalOcean Kubernetes MCP is connected.

Select the tools your AI agents can call

16 tools from the DigitalOcean Kubernetes MCP schema.

Showing 16 tools

doks-get-clusterreadGet information about a specific Kubernetes cluster.
doks-list-clustersreadList all Kubernetes clusters.
doks-create-clusterwriteCreate a new Kubernetes cluster.
doks-update-clusterwriteUpdate a Kubernetes cluster.
doks-delete-clusterhigh riskDelete a Kubernetes cluster.
doks-upgrade-clusterwriteUpgrade a Kubernetes cluster.
doks-get-cluster-upgradesreadGet available upgrades for a cluster.
doks-get-kubeconfigreadGet kubeconfig for a cluster.
doks-get-credentialsreadGet credentials for a cluster.
doks-create-nodepoolwriteCreate a new node pool in a cluster.
doks-get-nodepoolreadGet a node pool in a cluster.
doks-list-nodepoolsreadList all node pools in a cluster.
doks-update-nodepoolwriteUpdate a node pool in a cluster.
doks-delete-nodepoolhigh riskDelete a node pool in a cluster.
doks-delete-nodehigh riskDelete a node from a node pool.
doks-recycle-nodeswriteRecycle specific nodes in a node pool.

What DigitalOcean Kubernetes MCP exposes

DigitalOcean Kubernetes MCP groups its 16 tools into 3 categories, each with a suggested starting policy.

All 16 tools as JSON, ready to paste.

Category	Covers	Access	Suggested policy
Clusters	Cluster listing, details, creation, updates and deletion	Read / Write	Require approval for creation and deletion
Node Pools	Node pool listing, details, creation, resizing, recycling and deletion	Read / Write	Approve node pool changes; they affect capacity and cost
Access & Upgrades	Kubeconfig, credentials, available upgrades and upgrade execution	Read / Write	Treat kubeconfig as a credential; approve upgrades

Connect DigitalOcean Kubernetes MCP to your AI agent

Four steps, under ten minutes.

01
Sign in to NeuralTrust
Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.
02
Choose your agent
When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.
03
Connect DigitalOcean Kubernetes
Find DigitalOcean Kubernetes in the tool list and connect it.
04
Connect your agent
Follow the steps on screen to add the config to your agent, then send the test prompt.

Permissions down to the single tool

You do not allow DigitalOcean Kubernetes MCP or block it. You allow the exact tools each agent can call, one by one.

DigitalOcean Kubernetes MCP	16 TOOLS AVAILABLE
Code review agent	4 tools, read only
Issue triage bot	9 tools
Platform team assistant	all 16 tools

Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
Default denyA tool you have not enabled is never exposed to the agent.
Approval on writesTools that change or delete things can require a human to confirm.

Is DigitalOcean Kubernetes MCP secure?

One endpoint instead of raw credentials. Every call is checked against policy and logged.

AI agentsConnect through your MCP client configuration.	NeuralTrustApply controls based on your configuration.	DigitalOcean Kubernetes MCP16 documented tools.
Coding assistants	Connection & credentialsper user	Node Pools7 tools
Internal copilots	Tool access policiesdeny by default	Clusters5 tools
Workflow automations	Request & response inspectioninline	Access & Upgrades4 tools
Compatible MCP clients	Activity monitoringalerts and logs