Compatible with every major AI agent and IDE
What is the Linode (Akamai) MCP Server?
Connect your Linode (Akamai) account to any AI agent to manage your cloud infrastructure through natural language. This server provides comprehensive tools for compute and container orchestration.
What you can do
- Compute Management — List, create, view, update, and delete Linode instances (VPS) across global regions using
list_linodesandcreate_linode. - Kubernetes (LKE) — Deploy and manage Linode Kubernetes Engine clusters, including node pool configuration via
create_lke_cluster. - Account Oversight — Retrieve account details and list authorized users with
get_accountandlist_usersto maintain security and visibility. - Instance Control — Provision servers with specific images (like Ubuntu 22.04) and hardware types instantly.
How it works
- Subscribe to this server
- Enter your Linode Personal Access Token
- Start managing your cloud resources from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps Engineers — quickly check cluster statuses or spin up temporary environments without leaving the terminal or IDE.
- Full-stack Developers — manage backend infrastructure directly from the code editor while building applications.
- Cloud Architects — audit account resources and user access through conversational queries.
Built-in capabilities (10)
Create a new Linode
Create an LKE Cluster
Delete a Linode
View Account Details
View a specific Linode
View an LKE Cluster
List all Linodes (Compute Instances)
List LKE Clusters
Manage Users
Update a Linode
Why VS Code Copilot?
GitHub Copilot Agent mode brings Linode (Akamai) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Linode (Akamai) in VS Code Copilot
Linode (Akamai) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Linode (Akamai) to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Linode (Akamai) in VS Code Copilot
The Linode (Akamai) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Linode (Akamai) for VS Code Copilot
Every tool call from VS Code Copilot to the Linode (Akamai) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I list all my active virtual servers across all regions?
Yes. Use the list_linodes tool to retrieve a complete list of all Linode compute instances associated with your account, including their status and IP addresses.
How do I deploy a new Kubernetes cluster using this server?
You can use the create_lke_cluster tool. You'll need to provide a label, region, and Kubernetes version. You can also optionally define node pools with specific instance types.
Is it possible to delete a Linode instance if it's no longer needed?
Yes, the delete_linode tool allows you to permanently remove a specific Linode instance by providing its unique linodeId.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Linode (Akamai)
10 toolsManage Linode cloud infrastructure—provision compute instances, manage Kubernetes clusters (LKE), and monitor account details directly from your AI agent.

HTML DOM Query Engine
1 toolsExtract specific text and attributes from massive HTML payloads instantly using CSS selectors. Fast, memory-efficient DOM parsing.

LicenseCheck API
4 toolsSearch software licenses — audit permissions and conditions via AI.

Metrc
10 toolsCannabis track-and-trace via Metrc — track facilities, items, plants, and harvests.
