Linode MCP Server

A Model Context Protocol (MCP) server for interacting with Linode's API to manage cloud resources. This package enables Large Language Models (LLMs)

Local serverstdio

What is the Linode MCP MCP server?

Linode MCP becomes available to MCP clients through the linode mcp mcp server. A Model Context Protocol (MCP) server for interacting with Linode's API to manage cloud resources. This package enables Large Language Models (LLMs) like Claude to manage Linode instances through a standardized interface.

What Linode MCP does

A Model Context Protocol (MCP) server for interacting with Linode's API to manage cloud resources. This package enables Large Language Models (LLMs) like Claude to manage Linode instances through a standardized interface.

Key capabilities

  • List Linode regions, instance types, and instances
  • Create, view details, delete, and reboot Linode instances
  • Secure and easy-to-use interface for LLMs to manage Linode resources
  • Fully compatible with MCP-enabled AI assistants like Claude

Tools it exposes

Once connected, the assistant can call these 7 tools directly:

  • list_regions — List all available Linode regions
  • list_instance_types — List all available Linode instance types and their pricing
  • list_instances — List all existing Linode instances
  • create_instance — Create a new Linode instance
  • get_instance — Get details about a specific Linode instance
  • delete_instance — Delete a Linode instance
  • reboot_instance — Reboot a Linode instance

Installing the linode mcp mcp server

The server is distributed via PyPI as pip, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply one environment variable: LINODE_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Linode MCP sits in that group, and the shape of its toolset — list_regions, list_instance_types, list_instances among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • With 7 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Linode MCP.
  • Maintained by komer3.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the linode mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
list_regionsList all available Linode regions
list_instance_typesList all available Linode instance types and their pricing
list_instancesList all existing Linode instances
create_instanceCreate a new Linode instance
get_instanceGet details about a specific Linode instance
delete_instanceDelete a Linode instance
reboot_instanceReboot a Linode instance

How to install the Linode MCP MCP server

{
  "mcpServers": {
    "linode": {
      "command": "uvx",
      "args": ["pip"],
      "env": {
        "LINODE_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
LINODE_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Linode MCP to list regions.
  • Use Linode MCP to list instance types.
  • Use Linode MCP to list instances.

Frequently asked questions

It connects Linode MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 7 tools (list_regions, list_instance_types, list_instances, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Linode MCP directly.