linode-mcp-server

Linode MCP Server

Linode cloud resources become accessible to AI assistants through tools for compute, storage, networking, DNS, and databases. The project serves Linode users who want to inspect infrastructure and perform management tasks through conversation.

Server facts

linode-mcp-server

Project

Author
takashito
License
MIT

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
21
Last commit
Data as of

Overview

Compute administration anchors linode-mcp-server’s Linode workflows: an assistant can inspect instances, create or resize them, control their power state, and work with disks, configuration profiles, snapshots, and backups. Related tools cover attaching storage volumes, adjusting firewall rules, managing network interfaces, and configuring NodeBalancer ports and nodes. For application infrastructure, the project also exposes DNS records, object storage operations, and managed database tasks. These capabilities let Linode users bring resource inspection and infrastructure changes into conversations with clients such as Claude Desktop or VSCode Copilot Agent.

Tool categories can be enabled selectively, so a session focused on instances and volumes need not expose unrelated account or database tools. The documentation highlights this selection as a way to limit the tool definitions consuming client context. Connections support stdio and streaming HTTP. Authentication uses a Linode API token, with HTTP request headers taking priority over server-side token fallbacks. Shared deployments can accept each client’s token; requiring that approach means removing configured fallbacks. Some documented endpoints are beta or depend on features being enabled for the Linode account.

linode-mcp-server setup notes

  • linode-mcp-server records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers