Skip to main content
Glama
822,265 tools. Updated 2026-11-22 23:23

"DigitalOcean" matching MCP tools:

  • List instance types (server sizes) with vCPUs, RAM, disk and price. Without cluster_id this is the offline catalogue: snapshot prices and NO availability - a type listed here can be out of stock in a location, so never treat it as orderable. With cluster_id it reads the live stock at that cluster's location through the cluster's own credential (Hetzner today; other providers answer the catalogue marked availability unknown): every type carries available, and available=false means it cannot be created there now. To right-size or grow a cluster: read the workloads' requests first (the pods on the group's nodes and their CPU/memory requests), then call this with cluster_id, then propose the cheapest available type whose allocatable (a little under its RAM) fits the busiest node's summed requests. Never propose a type with available=false; update_node_group and add_node_group refuse one before the card is raised. Also use it to help the user choose control plane, worker and bastion sizes for a new cluster. The catalogue covers Hetzner, OVH, UpCloud and Scaleway only: this tool lists no DigitalOcean, AWS or Ankra Cloud sizes yet (the portal's create and node-group forms read those live from the provider).
    ConnectorOAuth
  • List the provisioned VM nodes of an Ankra-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, Ankra Cloud, Proxmox, or HPE Morpheus): every control-plane and worker server plus the cluster's single bastion/gateway node, with id, name, role, node group, instance type, observed Kubernetes version, location, lifecycle state, IPs, and the cloud provider's live status/power state when available. Use this before restart_node to find the exact node to target - each node's 'is_bastion_or_gateway' flag identifies the bastion/gateway even though its name varies by cluster. The per-node kubernetes_version identifies which nodes sit on the wrong side of a kubelet version skew. Deleted machine rows (workers a scale down or a stop removed) are left out unless include_deleted is true; deleted_nodes_omitted says how many were. Not available for imported (non-Ankra-provisioned) or managed-Kubernetes clusters. Read-only.
    ConnectorOAuth
  • Diagnose one Kubernetes node of an Ankra-provisioned cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, or Ankra Cloud) at the OS level over SSH-via-bastion, for failures below the Kubernetes layer that kubectl-style tools cannot see: a NotReady node whose kubelet stopped posting status, a node the reconcile history reports as ssh_unreachable, a crash-looping k3s/kubelet service. Returns a read-only diagnostics snapshot (systemd unit state, recent journal, kubectl node view, network and listener state, apiserver firewall drops) plus any node-recovery symptoms detected. If the node cannot be reached over SSH at all, the report instead carries a path_diagnosis naming the hop that failed (bastion or node), the cause class (connect_timeout, connection_refused, no_route, auth_rejected, handshake_failed, tunnel_prohibited, ...) and the verbatim dial error - use it to tell a dead bastion from a dead node from a rejected SSH key before recommending anything. Hetzner diagnoses of an unreachable node additionally include a firewall_inspection: which Hetzner Cloud Firewalls are applied to the bastion and node servers and whether they admit inbound TCP 22 (these firewalls filter the public interface only, so they can block the platform's hop to the bastion but never the private bastion-to-node hop). Runs nothing that changes the node. Identify the node with node_id (preferred, from list_cluster_nodes) or node_name; the bastion/gateway has no kubelet - use diagnose_bastion for it. Use this before ssh_repair_node. Not available for imported or managed-Kubernetes clusters, nor (yet) Proxmox/HPE Morpheus.
    ConnectorOAuth
  • Run one allowlisted, read-only kubectl command INSIDE an Ankra-provisioned cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS or Ankra Cloud) by executing it on a control-plane node over SSH-via-bastion, using that node's own admin kubeconfig. REACH FOR THIS ONLY WHEN THE CLUSTER'S AGENT IS NOT ANSWERING. While the agent is checking in, a get, describe, logs or events call here is REFUSED and names the tool to use instead: get_pods or cluster_query, describe_resource, get_pod_logs, get_events. Those answer the same question in one call, while this one dials the bastion, runs kubectl as cluster-admin and holds a scheduler job for up to 90 seconds. When the agent stops checking in they stop being an option - get_pod_logs and query_logs refuse outright, and the resource reads fall back to a cached inventory from before the outage - and this becomes the only live view left, because it does not use the agent at all; every result is stamped source=break_glass_ssh with executed_at. That is the state to use it in: to find out what is actually wrong with the agent itself - is its Deployment rolled out, is its pod Pending or CrashLoopBackOff or bound to a dead node, what do its logs and events say. If the agent IS checking in and you still need this, it is because an agent-path read already failed this turn (CLUSTER_OFFLINE, NO_AGENT or AGENT_TIMEOUT) or the tool it named refuses what you asked it for - get_pod_logs serves previous=true only on agent 2.1.1058 or newer, and refuses below it: set agent_path_unavailable=true, which is honoured and recorded. Verbs: get, describe, logs, events, top, version, api_resources, rollout_status. This is an allowlist, not a shell: there is no exec, port-forward, apply, patch, edit, create, scale, drain, cp, --raw, jsonpath or go-template, and no way to pass raw flags. Structured output (yaml/json) of Secrets is refused, though get and describe of them still report names, types and key names. Output is capped and credential-shaped strings are redacted. The command runs on a control-plane node, chosen automatically unless you pass node_id/node_name. Not available for imported or managed-Kubernetes clusters (they have no bastion), nor (yet) Proxmox/HPE Morpheus. Read-only: use ssh_kubectl_recover to change anything.
    ConnectorOAuth
  • Run one allowlisted STATE-CHANGING kubectl command inside an Ankra-provisioned cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS or Ankra Cloud) from a control-plane node over SSH-via-bastion, for recovering a cluster whose in-cluster ankra-agent is offline and which therefore cannot be reached any other way. Verbs, and when each is the right one: rollout_restart (the agent Deployment exists and looks healthy to its ReplicaSet but never checks in - the usual fix); rollout_undo (the agent self-upgraded and the new revision never checked in - roll back to the revision that worked); delete_pod (one named pod is stuck Terminating, or is bound to a node that is gone, so the ReplicaSet will not replace it); cordon and uncordon (stop scheduling onto a sick node, or allow it again). This is an allowlist, not a shell: it cannot exec, apply, patch, scale, drain or delete anything other than exactly one named pod, and it accepts no label selector on the delete path, so a mistaken confirmation costs at most one pod. Call ssh_kubectl_read FIRST to confirm what is actually broken - restarting a rollout that is failing to pull an image just repeats the failure. This changes a production cluster and requires confirmation. Not available for imported or managed-Kubernetes clusters, nor (yet) Proxmox/HPE Morpheus.
    Connector
    Destructive
    OAuth
  • Read the cloud-init status and the tail of /var/log/cloud-init-output.log for one node of an Ankra-provisioned cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, or Ankra Cloud), over SSH-via-bastion. This is the debug surface for node-group user_data: that document runs once, at first boot, before anything else can observe it, so a failed provisioning script is invisible to every other tool - the node either joins looking perfectly healthy (cloud-init's growpart fallback restores an ordinary full-disk root when a carve fails) or never appears at all. Use it when a node group carries user_data and a node came up wrong: partitions or mounts that are missing, a package that should have been installed, a first-boot script whose effect is absent. Returns cloud-init's own status (including whether it reported an error) plus the output-log tail, and runs nothing that changes the node. Repeated calls attach to an in-flight fetch instead of dispatching a duplicate. Identify the node with node_id (preferred, from list_cluster_nodes) or node_name. Not available for imported or managed-Kubernetes clusters. For OS-level failures unrelated to first boot, use ssh_diagnose_node.
    ConnectorOAuth

Matching MCP Servers

Matching MCP Connectors

  • Build, deploy, manage, and troubleshoot applications and infrastructure on DigitalOcean.

  • Create, list and destroy hourly-billed servers on Vultr, DigitalOcean, Hetzner and Linode.

  • Inspect the etcd cluster membership of an Ankra-provisioned cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, or Ankra Cloud) by running a read-only inspection on one control-plane node over SSH-via-bastion: the member list (hex and decimal ids, names, peer/client URLs, learner flag), each member's health, any active etcd alarms, and a quorum summary (voting members, healthy voters, quorum size, has_quorum plus the quorum_evidence it rests on, and failure_tolerance - healthy voters minus quorum size, floored at 0). failure_tolerance counts only voters observed serving, so it is a conservative lower bound: a voter whose health is unknown does not count towards it (health_unknown_voting_members says how many), and 0 can mean either no margin left or quorum already lost. Member health is three-valued: 'health' is 'serving', 'not_serving', or 'unknown' when no signal was readable at all, in which case 'healthy' is null rather than false - report unknown as unknown, never as down - and 'health_source' names the signal that decided it: 'client_endpoint' (the member's own client endpoint), 'local_health' (this node's own /health, for the member of the node the inspection runs on), 'raft_peer_link' (the local etcd's raft peer link to that member), 'member_list' (the member has no client endpoint because it never started), or 'unavailable' (no signal was readable at all). Use it BEFORE touching a degraded control-plane node, to know the quorum margin; and before remove_etcd_member, to get the member id. Identify the node to run on with node_id (preferred, from list_cluster_nodes) or node_name - it must be a control-plane node, and when one control-plane node is down, pick a HEALTHY peer (the inspection talks to the local etcd of the node it runs on). Runs nothing that changes the cluster. Not available for imported or managed-Kubernetes clusters, nor (yet) Proxmox/HPE Morpheus.
    ConnectorOAuth
  • Remove one member from the etcd cluster of an Ankra-provisioned cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, or Ankra Cloud) - the cleanup step when a dead control-plane node is being replaced: its stale etcd member must be removed before a replacement joins, or quorum math breaks. Executes on a HEALTHY control-plane peer (node_id/node_name - never the node whose member is being removed) over SSH-via-bastion; a node that is not control-plane is refused before any removal is attempted. The scheduler re-reads live membership immediately before acting and REFUSES to remove: a member still observed serving (by any health source, not only its own endpoint), a member whose health could not be read at all (unknown is not dead), the member of the node the command runs on, an id that does not uniquely match, or any non-learner voter whose removal would leave fewer healthy voters than the post-removal quorum - a refusal comes back as a structured result explaining why, with the live member list as evidence. This is an irreversible control-plane change: a removed member cannot rejoin with its old identity. Call get_etcd_members first and pass the member_id it listed (hex or decimal). Not available for imported or managed-Kubernetes clusters, nor (yet) Proxmox/HPE Morpheus.
    Connector
    Destructive
    OAuth
  • Scale the workers of an Ankra-provisioned self-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, Ankra Cloud, Proxmox VE, or HPE Morpheus). With node_group_name, scales that node group to worker_count (0-100; the target is clamped into the group's autoscaling bounds when autoscaling is enabled); without it, performs the legacy whole-cluster scale to worker_count (1-10; refused while any node group has autoscaling enabled - scale the group directly instead). The cluster must be online and free of in-progress operations. New workers provision in the background. On scale-down the highest-index workers drain one at a time through the eviction API, honouring PodDisruptionBudgets, and are then terminated; a worker whose drain a PodDisruptionBudget refuses is kept in service and the scale-down is withdrawn for it, so the group can settle above worker_count. Call list_node_groups first to see the current counts, and again afterwards to confirm them.
    Connector
    Destructive
    OAuth
  • Stop an Ankra-provisioned self-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, Ankra Cloud, Proxmox VE, or HPE Morpheus). On Hetzner, OVH, UpCloud, DigitalOcean, Proxmox VE and Morpheus a stop TERMINATES every VM of the cluster at the provider (control planes, workers, bastion/gateway); on Scaleway, AWS and Ankra Cloud the servers are instead powered off and kept with their volumes (etcd and the cluster's state survive; retained storage, gateway and IPs remain billable). On the terminating providers the platform first captures the cluster's state - an encrypted etcd snapshot uploaded to the organisation's backup vault - and tears the VMs down only once it is stored (k3s and kubeadm clusters on Hetzner, OVH, UpCloud, DigitalOcean, Proxmox VE and Morpheus); start_cluster then restores it so Secrets, ConfigMaps, custom resources and PersistentVolume/Claim bindings come back and StatefulSets reattach their existing cloud disks. preserve_state=false skips the capture (data on the VMs' disks is then destroyed; only the cluster's Ankra configuration is preserved and start_cluster re-provisions from it); preserve_state=true refuses a stop whose state cannot be captured. Cloud block volumes are never deleted by a stop. mode 'pause' (k3s on Hetzner, UpCloud and DigitalOcean) instead powers the servers off and keeps them with their disks, exactly like a Scaleway, AWS or Ankra Cloud stop: etcd, local data and the nodes' identities survive and start_cluster powers them back on, at the price of compute and storage still billing while paused - offer it when the user wants a short stop with everything intact, and the default teardown when they want to stop paying for the VMs. Use before change_control_plane on a single-controller cluster (a 3-controller cluster resizes live without stopping). Confirm with the user before calling.
    Connector
    Destructive
    OAuth
  • Restart one provisioned VM node of an Ankra-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, Ankra Cloud, or Proxmox) - a control-plane node, a worker, or the cluster's bastion/gateway. Schedules a native reboot (falling back to a power cycle) through the cloud provider API as a tracked operation; the node must be in the 'up' state and have no restart already in flight. Workloads on the node are briefly unavailable while it reboots. This is the fix for a VM that is hung or powered off - the case where SSH cannot reach the node at all. It is not a remedy for failed addon/manifest deploys or an unresponsive cluster agent, which ride the agent's outbound message-bus connection rather than node SSH. Identify the node with node_id (preferred, from list_cluster_nodes), node_name (exact match), or target="bastion" (the cluster's singleton bastion/gateway, no name needed). Always call list_cluster_nodes first if you do not already have the node_id. Not supported for HPE Morpheus or non-Ankra-provisioned clusters.
    Connector
    Destructive
    OAuth
  • List a cluster's power schedules: the scheduled one-off or repeated stop/start actions attached to an Ankra-provisioned self-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, Ankra Cloud, Proxmox VE, or HPE Morpheus). Each entry shows its id, action (stop or start), schedule_kind ('once' fires at run_at; 'cron' fires per cron_expression in timezone), enabled flag, next_run_at, and the outcome of its last run (completed, skipped, deferred, or failed, with detail). Use it before create_power_schedule (to avoid duplicates - at most 20 schedules per cluster) and to get the schedule_id for update_power_schedule / delete_power_schedule. Read-only. Not available for managed-Kubernetes or plain imported clusters.
    ConnectorOAuth
  • Create and provision a new MANAGED Kubernetes cluster - the cloud provider operates the control plane. Providers: eks (AWS), aks (Azure), gke (GCP), doks (DigitalOcean), uks (UpCloud), ovh_mks (OVH), kapsule (Scaleway; only for organisations with Scaleway enabled), ankracloud_k8s (Ankra Cloud Kubernetes; only for organisations with Ankra Cloud enabled); this is the ONLY way to create clusters on AWS, Azure, or GCP. Requires a provider credential (optional for ankracloud_k8s, which uses the organisation's built-in Ankra Cloud credential), a location slug, and at least one node pool ({name, size, count}); use list_managed_k8s_options first to resolve locations, versions, and node sizes. Optional: kubernetes_version, ha (DOKS only), cluster_plan (UKS only), kapsule.private_network_id (required for Kapsule). The cluster begins provisioning at the provider immediately after confirmation.
    Connector
    Destructive
    OAuth
  • Raise a cloud-provider limit for a credential, or produce the exact request a person has to submit when the provider has no API for it. Call get_provider_quotas first: it names the dimensions and says whether the provider is automatable. Azure is the only provider Ankra can submit to (through the Microsoft.Quota API); for Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, Proxmox VE and HPE Morpheus this call still SUCCEEDS and returns status manual_action_required with a manual_action object holding the console URL, the navigation path and a ready-to-paste request_text pre-filled with the live numbers - relay that to the user rather than retrying. One call may at most double a limit (or add 16 to a small one); ask for more by repeating the call. The limit can only go up: this tool will not lower one.
    Connector
    Destructive
    OAuth
  • Dry-run the rolling OS security-patch lane on an Ankra-provisioned cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS or Ankra Cloud): on every node and the bastion it simulates the pending apt upgrades against the package lists the host already has and changes nothing. Ankra's unattended upgrades deliberately hold back the packages whose updates restart networking in place (systemd, udev, netplan, the container runtime, iptables/nftables), so their security fixes only arrive through run_os_patches; this shows what is waiting. Per host: the pending, security and held-back packages, whether a reboot is owed, how old the package lists are, and a stateful_verdict - would_skip names the single-replica workloads with volumes (or the database node pool) that make run_os_patches skip the node unless include_stateful_nodes is true. It also returns the order a run would take (control planes first, one at a time, then the workers, the bastion last), the hosts a run would leave out and why (a node that is not up, a cluster's only control plane), and the cluster's patch policy. A host whose status is not success has an unknown plan, not an empty one. It waits about 40 seconds for the hosts; when completed is false, call get_os_patch_status a minute later for the finished plan.
    ConnectorOAuth
  • Scan code, config, logs, diffs or prompts for leaked credentials before you commit, share or send them to an LLM: 50+ rules (AWS, GitHub, GitLab, Slack, Stripe, Google, OpenAI, Anthropic, xAI, Hugging Face, npm, PyPI, Twilio, Telegram, Discord, DigitalOcean, Vault, database URLs, JWTs, PEM private keys) plus crypto-wallet secrets (EVM/Solana hex and base58 keys, Solana keypair arrays, checksum-validated Bitcoin WIF, seed phrases) and entropy-checked generic password assignments. Findings carry line/column, severity, entropy and a redacted preview (secrets are never echoed); placeholders and documented example keys are marked; optional fully redacted copy of the input. Returns JSON with: clean, findingCount, bySeverity, truncated, redacted, findings. Price: $0.003 USDC per successful call (x402, Base or Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/secret-scan
    ConnectorNo auth
  • Compare every server and bastion record the platform keeps for an Ankra-provisioned cluster (Hetzner, UpCloud, DigitalOcean, AWS, or Ankra Cloud) with what the cloud provider and the Kubernetes Node list say, and classify each record. Use it when a node group counts a worker that is not in the Node list, when unregistered_workers or a stale node / server record / phantom worker is suspected, when a worker sits in creating or stopping for days, or when a stopped cluster's kept machine may have been deleted at the provider. Each row carries name, resource_id, kind, role, node_group, state, parked (a kept row of a stopped cluster), machine_id, provider_answer (present, absent, unknown, or not_asked), node (registered, missing, unknown, or not_applicable) and classification: 'consistent'; 'phantom' (a live row whose machine the provider answered 404 for while answering another machine of the cluster as present in the same pass); 'gone_kept' (the same proof for a parked row); 'no_node' (the machine exists but no Node registered for it past a 30-minute grace); or 'unknown' (no recorded machine id, the provider did not answer, a 404 with no present machine to confirm it, or past the lookup cap). Unknown is never gone: report it as unknown. retirable_resource_ids lists the phantom and gone_kept rows; pass them to retire_gone_machine_rows. nodes_without_row lists Nodes no live record registers as. At most 40 machines are looked up per call, 4 at a time; rows_total and machines_looked_up say when the cap was reached. Runs nothing that changes the cluster or the provider. Not available for imported or managed-Kubernetes clusters, nor (yet) OVH, Scaleway, Proxmox or HPE Morpheus.
    ConnectorOAuth
  • Retire platform server records of an Ankra-provisioned cluster (Hetzner, UpCloud, DigitalOcean, AWS, or Ankra Cloud) whose machine the cloud provider no longer has - the fix for a phantom worker or a stale server record get_cluster_machine_inventory classified 'phantom' or 'gone_kept'. Pass the resource_ids it listed in retirable_resource_ids (at most 20 per call). The scheduler proves every row gone again at write time and retires it ONLY when the provider answers 404 for the row's recorded machine id AND answers another machine of the same cluster as present in the same pass; any other answer - a timeout, an auth error, a 404 with nothing to confirm it, or the machine still present - leaves the row untouched and says why. A live worker record becomes down and permanently deleted together with its per-node Kubernetes record, and a node group without autoscaling whose last worker it was releases its settings, as a normal worker delete does; a parked worker record of a stopped cluster is marked for permanent deletion together with its parked per-node Kubernetes record, so a start does not try to bring either back. A control-plane or bastion record, live or parked, is never retired, and a record that changed since the proof (re-pointed at another machine, resurrected, or with a job in flight on it) is left alone. The machine itself is not touched - the provider already deleted it. The Kubernetes Node object, if one lingers, is not deleted. The report lists every row by name with retired true or false and the reason. Not available for imported or managed-Kubernetes clusters, nor (yet) OVH, Scaleway, Proxmox or HPE Morpheus.
    Connector
    Destructive
    OAuth
  • Report what a cloud-provider credential is still allowed to create: the per-dimension limits and usage of the account, project, subscription or region behind it, normalized across Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, Proxmox VE, HPE Morpheus and Azure. Call this when provisioning, a node-group scale-up or a load balancer fails for a reason that could be a provider limit, or before growing a cluster. Read limit_known on every dimension before drawing a conclusion: Hetzner and Scaleway expose NO limits through any API, so their dimensions carry usage only and limits_exposed is false - that is a documented provider gap, not zero headroom and not a failed read. increase_automatable says whether Ankra can raise the limit itself (Azure only) or whether a person has to; increase_instructions says exactly how.
    ConnectorOAuth
  • Repair one Kubernetes node of an Ankra-provisioned cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, or Ankra Cloud) at the OS level over SSH-via-bastion: restarts the node's Kubernetes service unit (k3s / k3s-agent / kubelet) wrapped in Ankra's node-recovery engine, which classifies the failure and applies the matched curated fix (clear a failed unit, extend a start timeout, kill stale listeners, unblock the apiserver firewall, re-bootstrap the kubelet), verifies, and retries once. This is a privileged, not-cleanly-reversible action on a production node and briefly disrupts its workloads, so it requires confirmation. It does NOT run arbitrary commands - only the curated recovery plan. Always call ssh_diagnose_node first to confirm the node is broken at the OS level (not merely unreachable via bastion, which a node reboot - restart_node - addresses instead). Identify the node with node_id (preferred) or node_name. Not available for imported or managed-Kubernetes clusters, nor (yet) Proxmox/HPE Morpheus.
    Connector
    Destructive
    OAuth
  • List the day-2 topology of an Ankra-provisioned self-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, Ankra Cloud, Proxmox VE, or HPE Morpheus) in one call: every worker node group (instance type, node count, scaling bounds, labels, taints, autoscaling settings), the control plane (count, instance type, supported counts, whether it can be changed right now and why not), and the legacy whole-cluster worker count. Call this before scale_workers, add_node_group, update_node_group, delete_node_group, or change_control_plane. Not available for imported or managed-Kubernetes clusters. Read-only.
    ConnectorOAuth