Labsco
MCP SERVER

Linode MCP Server

by takashito ↗

Manage a Linode account by conversation — instances, volumes, networking, NodeBalancers, VPCs, object storage, DNS, managed databases and Kubernetes clusters.

Cloud Resources & Infrastructure as Code✓ Verified
Summary
It covers nearly all of Linode, which is also the thing to plan for: 416 tools is a lot to carry into every turn.

Pass --categories so only the part you need loads — instances,volumes,regions for everyday compute work — and --list-categories to see what exists before you choose. On the HTTP transport, a token in the server's environment or a .env in its working directory quietly acts as a fallback when a client sends no Authorization header, so clear both if every client should bring its own.

What it is

A broad MCP server over the Linode API: 416 tools grouped into categories you switch on individually, running over stdio or HTTP streaming.

What you get
  • Compute: create, resize, clone, rebuild, boot, reboot and rescue instances, plus their config profiles, disks, backups and snapshots
  • Networking: IPv4 and IPv6 allocation and sharing, reverse DNS, firewalls with rules, devices, history and templates, VLANs, and the newer Linode interfaces
  • Load balancing and private networking: NodeBalancers with port configs and nodes, plus VPCs, subnets and their IP inventory
  • Managed databases: MySQL and PostgreSQL instances with credentials, SSL certificates, patching, suspend and resume, and PostgreSQL connection pools
  • Kubernetes: clusters and node pools, node recycling, kubeconfig, API endpoints and control-plane ACLs
  • Object storage: buckets and objects, access keys, ACLs, pre-signed URLs, bucket certificates and quota usage
  • DNS domains and records, custom images and share groups, StackScripts, tags, support tickets and Longview monitoring clients
  • Account and profile: users, IAM roles and permissions, delegation, API tokens, SSH keys, two-factor settings, invoices and events
  • Monitoring: alert definitions, notification channels, log streams and destinations, dashboards and service metrics
Requirements

A Linode API token, created in your Cloud Manager profile settings. Three ways to supply it, highest precedence first: an Authorization: Bearer header sent by the client (HTTP transport only), the --token flag, or the LINODE_API_TOKEN environment variable. stdio is the default transport; --transport http --port 8080 --endpoint /mcp --host 127.0.0.1 switches to HTTP streaming. Run it with npx @takashito/linode-mcp-server, or as a Docker container reading LINODE_API_TOKEN, PORT, ENDPOINT and CATEGORIES.

Setup effort

One command plus a key — npx @takashito/linode-mcp-server --token YOUR_LINODE_API_TOKEN, then supply credentials