Linode MCP Server

What is Linode MCP Server?

An MCP server that connects AI assistants to Linode cloud infrastructure, enabling natural‑language management of compute, networking, storage, databases, Kubernetes, DNS, and more. Built with FastMCP, it supports stdio and HTTP streaming transports.

How to use Linode MCP Server?

Install and run via npx @takashito/linode-mcp-server --token YOUR_LINODE_API_TOKEN. Set the API token via command‑line flag, environment variable LINODE_API_TOKEN, or a .env file. For HTTP transport, clients can pass the token in an Authorization: Bearer header. Optionally limit enabled tool categories with --categories to reduce token usage.

Key features of Linode MCP Server

• Manage Linode instances, volumes, networking, NodeBalancers, databases, Kubernetes, and more
• Supports both stdio and HTTP streaming (StreamableHTTP) transports
• Per‑request API token via Authorization header for multi‑user setups
• Tool category selection to control context window usage and API costs
• Docker deployment with environment‑variable configuration
• Automatically coerces string‑serialized JSON parameters to correct types

Use cases of Linode MCP Server

• List all instances in a specific region using natural language
• Create a new Linode instance or a load balancer for web servers
• Set up a managed MySQL or PostgreSQL database from a chat prompt
• Manage DNS records, firewalls, VLANs, and VPCs conversationally
• Deploy automation scripts (StackScripts) and manage support tickets

FAQ from Linode MCP Server

How do I provide my Linode API token?

You can pass it with --token YOUR_TOKEN, set the LINODE_API_TOKEN environment variable, use a .env file, or (for HTTP transport) include an Authorization: Bearer <token> header per request. Token precedence: header > --token > env > .env.

Can I limit the number of tools to save context window?

Yes. Use the --categories flag to enable only the tool categories you need (e.g., --categories instances,volumes,regions). The full manifest of all categories is ~80–120k input tokens; selective scoping reduces cost and prevents overflow.

What transport options are available?

The server supports stdio (default, for Claude Desktop) and HTTP streaming (StreamableHTTP, for web clients). You can customize the HTTP server’s host, port, and endpoint path.

Can I run the server in Docker?

Yes. Build the image with docker build -t takashito/linode-mcp-server . and run with environment variables LINODE_API_TOKEN, PORT, ENDPOINT, and CATEGORIES.

Does the server support multi‑user setups?

Yes. For HTTP transport, run the server without a hard‑coded token; each client sends its own Linode API token via the Authorization header, allowing multiple users to share one server instance.