Skip to main content
Glama
komer3

Linode MCP Server

by komer3

Servidor MCP de Linode

Versión de PyPI Licencia: MIT

Un servidor de Protocolo de Contexto de Modelo (MCP) para interactuar con la API de Linode y gestionar recursos en la nube. Este paquete permite que los Modelos de Lenguaje Grandes (LLM) como Claude gestionen instancias de Linode mediante una interfaz estandarizada.

Características

  • Enumere las regiones, los tipos de instancias y las instancias de Linode

  • Crear, ver detalles, eliminar y reiniciar instancias de Linode

  • Interfaz segura y fácil de usar para que los LLM administren los recursos de Linode

  • Totalmente compatible con asistentes de IA habilitados para MCP como Claude

Related MCP server: Hetzner Cloud MCP Server

Instalación y configuración

Establezca su clave API de Linode como una variable de entorno:

export LINODE_API_KEY=your_api_key_here

O utilice un archivo .env en el directorio del proyecto:

LINODE_API_KEY=your_api_key_here

Puedes generar una clave API desde Linode Cloud Manager .

De PyPI (recomendado)

pip install linode-mcp

Usando uv

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

De la fuente

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

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

Uso

Como herramienta de línea de comandos

# 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

Con Claude para escritorio

  1. Instalar el paquete:

    pip install linode-mcp
  2. Edite manualmente su archivo de configuración de Claude Desktop:

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

    • Ventanas: %APPDATA%\Claude\claude_desktop_config.json

    {
      "mcpServers": {
        "linode": {
          "command": "linode-mcp",
          "args": ["--api-key", "your_api_key_here"]
        }
      }
    }
  3. Reiniciar Claude para escritorio

  4. En una conversación con Claude, ahora puedes pedirle que:

    • Enumere sus instancias de Linode

    • Crear una nueva instancia de Linode

    • Obtener detalles sobre una instancia específica

    • Reiniciar o eliminar instancias

Ejemplos de indicaciones:

  • "Muéstrame todas mis instancias de Linode"

  • Crear un nuevo Linode de 2 GB en la región de Frankfurt con Debian 11.

  • "Reiniciar mi instancia con ID 12345"

Herramientas disponibles

El paquete proporciona estas herramientas MCP:

  • list_regions - Lista todas las regiones de Linode disponibles

Para añadir:

  • list_instance_types : enumera todos los tipos de instancias de Linode disponibles y sus precios

  • list_instances - Lista todas las instancias de Linode existentes

  • create_instance - Crea una nueva instancia de Linode

  • get_instance - Obtener detalles sobre una instancia específica de Linode

  • delete_instance - Eliminar una instancia de Linode

  • reboot_instance - Reiniciar una instancia de Linode

Desarrollo

Estructura del proyecto

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

Contribuyendo

¡Agradecemos sus contribuciones! No dude en enviar una solicitud de incorporación de cambios.

  1. Bifurcar el repositorio

  2. Crea tu rama de funciones ( git checkout -b feature/amazing-feature )

  3. Confirme sus cambios ( git commit -m 'Add some amazing feature' )

  4. Empujar a la rama ( git push origin feature/amazing-feature )

  5. Abrir una solicitud de extracción

Licencia

Este proyecto está licenciado bajo la licencia MIT: consulte el archivo de LICENCIA para obtener más detalles.

Expresiones de gratitud

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

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

Related MCP Connectors

Related MCP Servers