Skip to main content
Glama
enesjakozh
komer3

Linode MCP Server

by komer3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Linode MCP 服务器

PyPI 版本 许可证：MIT

一个模型上下文协议 (MCP) 服务器，用于与 Linode 的 API 交互以管理云资源。此软件包支持 Claude 等大型语言模型 (LLM) 通过标准化接口管理 Linode 实例。

特征

  • 列出 Linode 区域、实例类型和实例

  • 创建、查看详细信息、删除和重启 Linode 实例

  • 安全且易于使用的界面，方便 LLM 管理 Linode 资源

  • 与 Claude 等支持 MCP 的 AI 助手完全兼容

Related MCP server: Hetzner Cloud MCP Server

安装和配置

将您的 Linode API 密钥设置为环境变量：

export LINODE_API_KEY=your_api_key_here

或者使用项目目录中的.env文件：

LINODE_API_KEY=your_api_key_here

您可以从Linode Cloud Manager生成 API 密钥。

来自 PyPI（推荐）

pip install linode-mcp

使用 uv

uvx pip install linode-mcp
uvx linode-mcp --api-key $LINODE_API_KEY

来自源

# Clone the repository
git clone https://github.com/yourusername/linode-mcp.git
cd linode-mcp

# Install the package in development mode
./scripts/install.sh

用法

作为命令行工具

# Run with default settings
linode-mcp

# Enable debug logging
linode-mcp --debug

# Specify API key on command line
linode-mcp --api-key your_api_key_here

使用 Claude 桌面版

  1. 安装软件包：

    pip install linode-mcp

  2. 手动编辑您的 Claude Desktop 配置文件：

    • MacOS： ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows： %APPDATA%\Claude\claude_desktop_config.json

    {
  "mcpServers": {
    "linode": {
      "command": "linode-mcp",
      "args": ["--api-key", "your_api_key_here"]
    }
  }
}

  3. 重启 Claude 桌面版

  4. 在与 Claude 的对话中，您现在可以要求它：

    • 列出您的 Linode 实例

    • 创建新的Linode实例

    • 获取有关特定实例的详细信息

    • 重启或删除实例

提示示例：

  • “显示我所有的 Linode 实例”

  • “使用 Debian 11 在法兰克福地区创建一个新的 2GB Linode”

  • “重启我的 ID 为 12345 的实例”

可用工具

该软件包提供了以下 MCP 工具：

  • list_regions - 列出所有可用的 Linode 区域

待添加：

  • list_instance_types - 列出所有可用的 Linode 实例类型及其定价

  • list_instances - 列出所有现有的 Linode 实例

  • create_instance创建一个新的 Linode 实例

  • get_instance - 获取有关特定 Linode 实例的详细信息

  • delete_instance - 删除 Linode 实例

  • reboot_instance - 重新启动 Linode 实例

发展

项目结构

linode-mcp/
├── bin/                  # Command-line scripts
├── src/                  # Source code
│   └── linode_mcp/       # Main package
│       ├── tools/        # MCP tool implementations
│       └── server.py     # MCP server implementation
├── setup.py              # Package setup file
└── README.md             # This file

贡献

欢迎贡献代码！欢迎提交 Pull 请求。

  1. 分叉存储库

  2. 创建你的功能分支（ git checkout -b feature/amazing-feature ）

  3. 提交您的更改（ git commit -m 'Add some amazing feature' ）

  4. 推送到分支（ git push origin feature/amazing-feature ）

  5. 打开拉取请求

执照

该项目根据 MIT 许可证获得许可 - 有关详细信息，请参阅LICENSE文件。

致谢

Available Tools

1 tool
list_regionsA

List all available Linode regions

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description implies a read-only operation, but does not explicitly state behavioral traits such as idempotency, caching, or rate limits. With no annotations, this is adequate for a simple list tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with five words, perfectly concise and front-loaded. No unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the trivial nature (no parameters, simple list operation, output schema exists), the description provides complete context for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, so schema coverage is 100%. The description does not need to add parameter details. Baseline score of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List') and the resource ('all available Linode regions'), with no ambiguity. There are no sibling tools to distinguish from, so the purpose is precisely conveyed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when a full list of regions is needed, but does not explicitly state when to use or not use it, nor provide alternatives. Given no siblings, this is acceptable but not maximally helpful.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • Changedlist_regions1 field changed
      • addedInput schema / title
        Added value: +"list_regionsArguments"
  2. 1 tool update
    • First observedlist_regions
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'list_regions' has a clear and distinct purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

The naming follows a consistent verb_noun pattern ('list_regions'), and with only one tool, there is no inconsistency to evaluate. The pattern is clear and predictable for any potential future tools.

Tool Count2/5

A single tool is too few for a server named 'Linode MCP Server', which implies broader cloud management capabilities. This feels thin and incomplete for managing Linode resources, as it only covers region listing without any operations for instances, volumes, networking, or other core features.

Completeness1/5

The tool surface is severely incomplete for a Linode server. It only lists regions, missing essential CRUD operations for instances, volumes, networking, DNS, and other Linode services. This leaves significant gaps that will cause agent failures in typical cloud management tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers