It is worth being explicit because the feature list at the top of that README describes creating, rebooting and deleting instances, while the tool table further down puts all of those under "To be added". If you are choosing this to let an assistant manage running infrastructure, that is not what it does yet — region listing is. Version 0.0.1 is consistent with where the project actually is.
An early MCP server for Linode's API. What ships and works is region listing; the tools for instance types, instances, creation, details, deletion and reboot are listed in the README under "To be added", so the page you are reading is a snapshot of a project at its first step rather than a finished cloud console.
- Every available Linode region listed — `list_regions`
- Named as planned, not yet available: instance types with pricing, existing instances, instance creation, instance details, deletion and reboot — `list_instance_types`, `list_instances`, `create_instance`, `get_instance`, `delete_instance`, `reboot_instance`
A Linode API key, generated in the Linode Cloud Manager and supplied either as `LINODE_API_KEY` in the environment or a `.env` file, or as `--api-key` on the command line. Python: `pip install linode-mcp` gives you the `linode-mcp` command, which your client launches directly; `uvx linode-mcp --api-key $LINODE_API_KEY` works too. The package is `linode-mcp` (0.0.1) and `--debug` turns on verbose logging.
One command plus a key — pip install linode-mcp, then supply credentials