Linode MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINODE_API_KEY | Yes | Your Linode API key. Generate one from https://cloud.linode.com/profile/tokens |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_regionsA | List all available Linode regions |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of ambiguity or overlap with other tools.
The single tool uses a clear verb_noun pattern (list_regions), which is consistent and informative.
For a Linode server, one tool is far too few; users would expect many more operations like listing instances, creating resources, etc.
The server provides only a list of regions with no other CRUD or lifecycle operations, making it severely incomplete for any meaningful Linode management.