Compatible with every major AI agent and IDE
What is the Fly.io Extended MCP Server?
Connect your Fly.io account to any AI agent to orchestrate your cloud infrastructure through natural language. This server provides full access to the Fly Machines API, allowing for granular control over global deployments.
What you can do
- App Management — Create, list, and delete Fly Apps across your organizations.
- Machine Lifecycle — Start, stop, suspend, and update individual Machines with precise configuration control.
- Storage & Volumes — Provision, extend, and manage persistent volumes and snapshots for your stateful applications.
- Network & Security — Manage ACME and custom certificates, and request OIDC tokens for secure workload identity.
- Real-time Monitoring — Wait for specific machine states and fetch detailed metadata for debugging and orchestration.
How it works
- Subscribe to this server
- Enter your Fly.io Personal Access Token
- Start deploying and managing your global infrastructure from Claude, Cursor, or any MCP client
Who is this for?
- DevOps Engineers — Automate scaling, machine restarts, and volume management without leaving the terminal or chat interface.
- Full-stack Developers — Deploy new app instances and check machine statuses directly from your code editor.
- SRE Teams — Quickly inspect infrastructure health and manage certificates during incident response.
Built-in capabilities (28)
Trigger DNS validation check for a certificate
Request a Let's Encrypt certificate
Create a new Fly App
Import a custom PEM certificate
Create a lease for a Machine
Requires a config object containing at least the image. Create a new Fly Machine
Create a new volume
Delete a Fly App
Remove hostname and certificates
Delete a Machine
Delete a volume
Increase volume size
Get details about a Fly App
Get certificate details
Get Machine details
Get volume details
List Fly Apps
List all certificates for an app
List all Machines in an app
List volume snapshots
List all volumes in an app
Release a lease for a Machine
Request an OpenID Connect (OIDC) token
Start a Machine
Stop a Machine
Suspend a Machine
Update Machine configuration
Wait for a specific Machine state
Why VS Code Copilot?
GitHub Copilot Agent mode brings Fly.io Extended data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 28 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
Fly.io Extended in VS Code Copilot
Fly.io Extended and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Fly.io Extended 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 Fly.io Extended in VS Code Copilot
The Fly.io Extended 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 28 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
Fly.io Extended for VS Code Copilot
Every tool call from VS Code Copilot to the Fly.io Extended MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I start or stop a specific Fly Machine using this server?
Yes. You can use the start_machine and stop_machine tools by providing the app name and the specific Machine ID. You can also use suspend_machine for compatible workloads.
How do I create a new application in a specific organization?
Use the create_app tool. You will need to provide a unique app_name and the org_slug of the target organization where you want the app to be provisioned.
Is it possible to manage persistent storage volumes?
Absolutely. The server includes tools like create_volume, list_volumes, extend_volume, and delete_volume to handle the full lifecycle of your Fly Volumes.
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 →
Postmark
10 toolsEquip your AI to send emails, monitor delivery stats, track bounces, and manage Postmark templates directly from your chat.

BoxyHQ (Enterprise SSO)
8 toolsManage Enterprise SSO and Directory Sync (SCIM) via BoxyHQ — configure SAML/OIDC connections and automate user provisioning directly from your AI agent.

TarotAPI
6 toolsDraw tarot cards, get readings, and explore card meanings via AI.

Hologram.io
11 toolsAutomate IoT connectivity via Hologram.io — manage devices, SIM cards, and data usage directly from any AI agent.
