fly-mcp

Created By
brannna year ago
MCP server for managing your Fly.io infrastructure
Overview

what is fly-mcp?

fly-mcp is an open-source Model Context Protocol (MCP) server designed for managing Fly.io infrastructure, enabling AI-driven DevOps workflows through natural language interactions.

how to use fly-mcp?

To use fly-mcp, clone the repository from GitHub, set up your environment variables with your Fly.io API token and organization name, and then build and run the application. For production deployment, use the Fly.io MCP infrastructure commands.

key features of fly-mcp?

  • Open-source MCP server for Fly.io management
  • Supports natural language interactions for DevOps tasks
  • Flexible configuration through YAML files, environment variables, and command line flags
  • Core tools for managing Fly.io applications, including listing apps and checking status

use cases of fly-mcp?

  1. Managing Fly.io applications through a natural language interface.
  2. Automating DevOps workflows with AI-driven commands.
  3. Monitoring and scaling applications hosted on Fly.io.

FAQ from fly-mcp?

  • What is the required environment for fly-mcp?

You need Go 1.21 or later, a Fly.io account, and an API token.

  • Is fly-mcp free to use?

Yes! fly-mcp is open-source and free to use.

  • How can I contribute to fly-mcp?

Contributions are welcome! Please refer to the contributing guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
brannn
Star
0
Language
Go
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago