by takashito
Manage compute, volumes, networking & more with Li Node's robust cloud API. Easily control instances, domains, databases
Connects AI assistants like Claude to Linode's cloud infrastructure API for managing virtual machines and cloud resources through natural language conversations.
Linode is a community-built MCP server published by takashito that provides AI assistants with tools and capabilities via the Model Context Protocol. Manage compute, volumes, networking & more with Li Node's robust cloud API. Easily control instances, domains, databases It is categorized under databases, cloud infrastructure.
You can install Linode in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Linode is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Enable Claude to query your database directly using natural language
Example
Ask 'Show me top 10 customers by revenue this month' and get SQL results instantly
Eliminate manual SQL writing for ad-hoc queries, get insights 10x faster
Generate complex reports and analytics without leaving conversation
Example
Analyze sales trends, cohort retention, user behavior patterns conversationally
Democratize data access—non-technical team members can query databases
Understand database structure, relationships, and data models
Example
'Explain the user_orders table schema and its relationships'
Onboard engineers faster, explore unfamiliar databases efficiently
Share your MCP server with the developer community
Linode has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We wired Linode into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
According to our notes, Linode benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Strong directory entry: Linode surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Linode is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Useful MCP listing: Linode is the kind of server we cite when onboarding engineers to host + tool permissions.
Useful MCP listing: Linode is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Linode against two servers with overlapping tools; this profile had the clearer scope statement.
According to our notes, Linode benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Linode is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
showing 1-10 of 29
An MCP (Model Context Protocol) server that connects your AI Assistant or Agent to your Linode cloud infrastructure allowing you to manage your cloud resources through natural conversation. Built with FastMCP framework and supports stdio, SSE, and HTTP streaming transports!
Ask Claude Desktop or VSCode Copilot Agent to help you with tasks like:
This server provides tools for the following Linode service categories:
You'll need a Linode API token to use this server. Create one in your Linode Cloud Manager profile settings.
# Start the server with your API token
npx @takashito/linode-mcp-server --token YOUR_LINODE_API_TOKEN
You can provide your token in several ways:
Command line option:
npx @takashito/linode-mcp-server --token YOUR_LINODE_API_TOKEN
Environment variable:
export LINODE_API_TOKEN=your_token_here
npx @takashito/linode-mcp-server
Environment file:
Create a .env file in your project directory with:
LINODE_API_TOKEN=your_token_here
Then run:
npx @takashito/linode-mcp-server
Open Claude settings > Developer > Edit Config:
{
"mcpServers": {
"linode": {
"command": "npx",
"args": ["-y", "@takashito/linode-mcp-server", "--token", "YOUR_LINODE_API_TOKEN"]
}
}
}
Add to your settings.json:
{
"mcpServers": {
"linode": {
"command": "npx",
"args": ["-y", "@takashito/linode-mcp-server", "--token", "YOUR_LINODE_API_TOKEN", "--categories", "instances,volumes,regions"]
}
}
}
⚠️ Note: For GPT-4o based clients, use --categories to limit tools and avoid context window errors.
For the easiest setup, use Smithery:
npx -y @smithery/cli install @takashito/linode-mcp-server --client claude
You can selectively enabled tools with --categories parameter:
# Enable only instances and volumes tools
npx @takashito/linode-mcp-server --token YOUR_TOKEN --categories instances,volumes
Or in Claude Desktop config:
{
"mcpServers": {
"linode": {
"command": "npx",
"args": [
"-y",
"@takashito/linode-mcp-server",
"--token",
"YOUR_LINODE_API_TOKEN",
"--categories",
"instances,volumes,regions"
]
}
}
}
Available categories: instances, volumes, networking, nodebalancers, regions, placement, vpcs, objectStorage, domains, databases, kubernetes, images, stackScripts, tags, support, longview, profile, account
To see all available categories:
npx @takashito/linode-mcp-server --list-categories
stdio transport - Default transport compatible with Claude Desktop
# Default stdio transport
npx @takashito/linode-mcp-server --token YOUR_TOKEN
SSE transport - Server-Sent Events transport for web clients
# Start with SSE transport on port 3000 /sse
npx @takashito/linode-mcp-server --token YOUR_TOKEN --transport sse --port 3000 --endpoint /sse
httpStream transport - HTTP streaming transport for web clients
# Start with HTTP streaming transport on port 8080 /mcp
npx @takashito/linode-mcp-server --token YOUR_TOKEN --transport http --port 8080 --endpoint /mcp
You can customize port and host for both SSE and HTTP streaming transport:
--port : Server port (default: http: 8080, sse: 3000)--endpoint : Server Path (default: http: /mcp, sse: /sse)--host : Server host (default: 127.0.0.1)For http / sse transport, you can run mcp server without --token parameter.
# Start with HTTP streaming transport on port 8080 /mcp at localhost
npx @takashito/linode-mcp-server --transport http
Configure your mcp client to add Authorization Header. linode-mcp-server forward this API token to access Linode API at backend.
{
"mcpServers": {
"linode-remote-mcp": {
"command": "npx",
"args": [
"mcp-remote",
"http://localhost:8080/mcp",
"--header",
"Authorization: Bearer ${LINODE_API_TOKEN}"
],
"env": {
"LINODE_API_TOKEN": "..."
}
},
}
}
This MCP server provides the following tools for interacting with Linode API services:
Manage Linode compute instances, including creation, deletion, and power operations.
list_instances - Get a list of all Linode instancesget_instance - Get details for a specific Linode instancecreate_instance - Create a new Linode instanceupdate_instance - Update a Linode instancedelete_instance - Delete a Linode instancereboot_instance - Reboot a Linode instanceboot_instance - Power on a Linode instanceshutdown_instance - Power off a Linode instanceresize_instance - Resize a Linode instanceclone_instance - Clone a Linode instance to a new Linoderebuild_instance - Rebuild a Linode instance with a new imagerescue_instance - Boot a Linode instance into rescue modereset_root_password - Reset the root password for a Linode instanceinitiate_migration - Initiate a DC migration for a Linode instanceupgrade_linode - Upgrade a Linode instancelist_instance_configs - Get all configuration profiles for a Linode instanceget_instance_config - Get a specific configuration profile for a Linode instancecreate_instance_config - Create a new configuration profile for a Linode instanceupdate_instance_config - Update a configuration profile for a Linode instancedelete_instance_config - Delete a configuration profile for a Linode instancelist_config_interfaces - List all interfaces for a configuration profileget_config_interface - Get details for a specific configuration profile interfacecreate_config_interface - Create a new interface for a configuration profileupdate_config_interface - Update an interface for a configuration profiledelete_config_interface - Delete an interface from a configuration profilereorder_config_interfaces - Reorder interfaces for a configuration profilelist_instance_disks - Get all disks for a Linode instanceget_instance_disk - Get a specific disk for a Linode instancecreate_instance_disk - Create a new disk for a Linode instanceupdate_instance_disk - Update a disk for a Linode instancedelete_instance_disk - Delete a disk for a Linode instanceresize_instance_disk - Resize a disk for a Linode instanceclone_disk - Clone a disk to a new diskreset_disk_root_password - Reset a disk root passwordlist_backups - Get a list of all backups for a Linode instanceget_backup - Get details for a specific backupcreate_snapshot - Create a snapshot for a Linode instancecancel_backups - Cancel backups for a Linode instanceenable_backups - Enable backups for a Linode instancerestore_backup - Restore a backup to a Linode instanceget_networking_information - Get networking information for a Linode instanceallocate_ipv4_address - Allocate an IPv4 address for a Linode instanceget_ip_address - Get details for a specific IP addressupdate_ip_address_rdns - Update reverse DNS for an IP addressdelete_ipv4_address - Delete an IPv4 addresslist_linode_firewalls - List firewalls for a Linode instanceapply_linode_firewalls - Apply firewalls to a Linode instanceget_instance_stats - Get current statistics for a Linode instanceget_instance_stats_by_date - Get statistics for a Linode instance for a specific monthget_network_transfer - Get network transferRun data quality queries to catch anomalies and inconsistencies
Example
Find duplicate records, missing values, orphaned foreign keys automatically
Maintain data integrity with less manual SQL work
Prerequisites
Time Estimate
15-30 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server acts as bridge between Claude and database, translating natural language to SQL queries and returning results in structured format.
Protocols
Compatibility
✓ Use when
Use for ad-hoc data queries, exploratory analysis, report generation, schema exploration, and democratizing data access. Best for read-heavy analytics workloads.
✗ Avoid when
Avoid for production write operations, mission-critical transactions, real-time OLTP workloads, or when database contains sensitive PII without proper access controls. Use read replicas, not primary.