4,000+ servers built on vurb.ts
Vinkius
VS Code CopilotIDE
Linode (Akamai) MCP Server

Bring Vps
to VS Code Copilot

Learn how to connect Linode (Akamai) to VS Code Copilot and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Create LinodeCreate Lke ClusterDelete LinodeGet AccountGet LinodeGet Lke ClusterList LinodesList Lke ClustersList UsersUpdate Linode

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Linode (Akamai)

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_linodes and create_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_account and list_users to maintain security and visibility.
  • Instance Control — Provision servers with specific images (like Ubuntu 22.04) and hardware types instantly.

How it works

  1. Subscribe to this server
  2. Enter your Linode Personal Access Token
  3. 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_linode

Create a new Linode

create_lke_cluster

Create an LKE Cluster

delete_linode

Delete a Linode

get_account

View Account Details

get_linode

View a specific Linode

get_lke_cluster

View an LKE Cluster

list_linodes

List all Linodes (Compute Instances)

list_lke_clusters

List LKE Clusters

list_users

Manage Users

update_linode

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

See it in action

Linode (Akamai) in VS Code Copilot

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

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.

Linode (Akamai)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

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.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

07

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.

08

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 →