Linode MCP Server
Related Servers
Alternatives to Linode MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for managing Linode cloud resources via the Linode API, enabling LLMs to create, list, delete, and reboot instances.1MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that wraps the Linode API v4 for use in Claude Desktop, enabling management of Linode instances, volumes, DNS, and more via natural language.-
- AlicenseAqualityDmaintenanceA Model Context Protocol server that allows language models to manage Hetzner Cloud resources through structured functions, including servers, volumes, firewalls, and SSH keys.30138MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol (MCP) server that lets Claude manage Terraform infrastructure through natural language.1130 npm1MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables large language models to interact with Linear's issue tracking system, allowing management of issues, projects, teams, and other Linear resources.1913 npm1MIT
- AlicenseAqualityDmaintenanceA read-only MCP server for Akamai Cloud (Linode) that lets users ask plain-language questions about their account, including inventory, pricing, GPU availability, and account limits.37Apache 2.0
TDQS
Scored across 1 tool
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.
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.
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.
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.