2,500+ MCP servers ready to use
Vinkius

Fly.io Alternative MCP Server for Mastra AI 13 tools — connect in under 2 minutes

Built by Vinkius GDPR 13 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Fly.io Alternative through the Vinkius and Mastra agents discover all tools automatically — type-safe, streaming-ready, and deployable anywhere Node.js runs.

Vinkius supports streamable HTTP and SSE.

typescript
import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token — get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "flyio-alternative": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "Fly.io Alternative Agent",
    instructions:
      "You help users interact with Fly.io Alternative " +
      "using 13 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with Fly.io Alternative?"
  );
  console.log(result.text);
}

main();
Fly.io Alternative
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

About Fly.io Alternative MCP Server

Connect your Fly.io account to any AI agent and take full control of your edge compute infrastructure through natural conversation.

Mastra's agent abstraction provides a clean separation between LLM logic and Fly.io Alternative tool infrastructure. Connect 13 tools through the Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution — deployable to any Node.js host in one command.

What you can do

  • App Management — List all apps and retrieve their configuration details including regions, status and organization
  • Machine Lifecycle — Create, start, stop, restart, update and delete machines (VMs) with full control over CPU, memory, region and image
  • Machine Inspection — View machine state, configuration, services, health checks and IP addresses
  • Persistent Volumes — List and create persistent storage volumes that survive machine restarts and redeployments
  • Certificate Management — Review TLS/SSL certificates and their issuance status for app domains
  • Global Deployment — Deploy machines across Fly.io's global regions (iad, sjc, nrt, fra, syd, etc.) for low-latency access

The Fly.io Alternative MCP Server exposes 13 tools through the Vinkius. Connect it to Mastra AI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Fly.io Alternative to Mastra AI via MCP

Follow these steps to integrate the Fly.io Alternative MCP Server with Mastra AI.

01

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

Mastra discovers 13 tools from Fly.io Alternative via MCP

Why Use Mastra AI with the Fly.io Alternative MCP Server

Mastra AI provides unique advantages when paired with Fly.io Alternative through the Model Context Protocol.

01

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure — add Fly.io Alternative without touching business code

02

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

03

TypeScript-native: full type inference for every Fly.io Alternative tool response with IDE autocomplete and compile-time checks

04

One-command deployment to any Node.js host — Vercel, Railway, Fly.io, or your own infrastructure

Fly.io Alternative + Mastra AI Use Cases

Practical scenarios where Mastra AI combined with the Fly.io Alternative MCP Server delivers measurable value.

01

Automated workflows: build multi-step agents that query Fly.io Alternative, process results, and trigger downstream actions in a typed pipeline

02

SaaS integrations: embed Fly.io Alternative as a first-class tool in your product's AI features with Mastra's clean agent API

03

Background jobs: schedule Mastra agents to query Fly.io Alternative on a cron and store results in your database automatically

04

Multi-agent systems: create specialist agents that collaborate using Fly.io Alternative tools alongside other MCP servers

Fly.io Alternative MCP Tools for Mastra AI (13)

These 13 tools become available when you connect Fly.io Alternative to Mastra AI via MCP:

01

create_machine

io app. Requires the Docker image reference (e.g. "registry.fly.io/myapp:latest"). Optionally set the region (e.g. "iad", "sjc", "nrt"), CPU cores (1-16), memory in MB (256-8192), guest CPU kind (shared, performance) and services config. Machines start in stopped state — use start_machine after creation. Create a new machine in a Fly.io app

02

create_volume

Requires the volume name and size in gigabytes. Optionally set the region. The volume must be attached to a machine via the machine config mounts. Create a persistent volume for a Fly.io app

03

delete_machine

The machine cannot be recovered. Optionally set force=true to delete even if the machine has an attached volume. Provide the app_name and machine_id. WARNING: this action is irreversible. Delete a Fly.io machine permanently

04

get_app

io app including its name, status, regions, organization and network configuration. Provide the app name (not ID). Get details for a specific Fly.io app

05

get_machine

Provide both the app_name and machine_id. Get details for a specific Fly.io machine

06

list_apps

io account. Each app is a collection of machines (VMs) running your code across Fly.io's global edge network. Returns app name, status, region and creation date. Use the app name for all subsequent machine, volume and certificate operations. List all Fly.io apps

07

list_certificates

io app. Each certificate has a hostname, status (issued, pending, failed) and source (lets_encrypt, self_signed, acme). Use this to audit HTTPS certificate status for your app's domains. List TLS/SSL certificates for a Fly.io app

08

list_machines

io app. Each machine has an ID, name, state (started, stopped, created, destroyed), region, image reference, CPU/memory config and IP addresses. Machines are the fundamental compute units on Fly.io. List machines (VMs) for a Fly.io app

09

list_volumes

io app. Each volume has an ID, name, state, size in GB, region and the machine it is attached to. Volumes provide persistent storage that survives machine restarts. List persistent volumes for a Fly.io app

10

restart_machine

Useful for applying configuration changes or recovering from issues. Provide the app_name and machine_id. Restart a Fly.io machine

11

start_machine

The machine will boot and begin running its configured image. Provide the app_name and machine_id. Start a stopped Fly.io machine

12

stop_machine

The machine will stop and release its compute resources but retains its configuration and data. Provide the app_name and machine_id. Stop a running Fly.io machine

13

update_machine

You can modify the Docker image, CPU/memory allocation, services config, mounts and more. Provide the app_name, machine_id and a JSON body with the fields to update. Update a Fly.io machine configuration

Example Prompts for Fly.io Alternative in Mastra AI

Ready-to-use prompts you can give your Mastra AI agent to start working with Fly.io Alternative immediately.

01

"Show me all machines running in my web-api app."

02

"Start the stopped machine in Tokyo and restart the one in Frankfurt."

03

"Create a new 10GB volume called 'data' for my database app in Virginia."

Troubleshooting Fly.io Alternative MCP Server with Mastra AI

Common issues when connecting Fly.io Alternative to Mastra AI through the Vinkius, and how to resolve them.

01

createMCPClient not exported

Install: npm install @mastra/mcp

Fly.io Alternative + Mastra AI FAQ

Common questions about integrating Fly.io Alternative MCP Server with Mastra AI.

01

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
02

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
03

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

Connect Fly.io Alternative to Mastra AI

Get your token, paste the configuration, and start using 13 tools in under 2 minutes. No API key management needed.