Use Fly from Claude
Add the Fly connection to a Space that runs Claude, then use it from every channel in that Space.
Connect Fly once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Fly connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Fly connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Fly runs applications as lightweight machines across regions worldwide, giving teams control over deployment, networking, and scaling. With a Fly connection in type.com, a platform Space can ask Claude to check if an app name is free, set up a health check job, or add a WireGuard peer for private networking, directly from a thread.
Connect Fly once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Confirm a proposed Fly app name is available before the team commits to it in deployment scripts or documentation.
Check if the Fly app name acme-api-prod is available before we deploy.
Create a health check job that watches a new endpoint from multiple regions as soon as it goes live.
Create a Fly health check job for https://api.acme.com/health from three regions.
Connect a new piece of infrastructure to the Fly network by adding a WireGuard peer without leaving the thread.
Add a WireGuard peer for our staging organization in Fly so we can reach it privately.
Adds a WireGuard peer to a Fly organization for private networking between your infrastructure and Fly.
Confirms whether a proposed Fly app name is free to use before creating the app.
Retrieves scheduled check jobs, including their schedules, URLs, and configuration, with pagination support.
Reports whether the current token is limited to user access or also allows organization access.
Sets up automated monitoring for a URL, checking it from multiple geographic locations.
Fly.io runs applications as lightweight machines across global regions. Developer docs cover deploying apps, volumes, networking, secrets, Postgres, GPUs, Fly Machines, GraphQL/REST-style APIs, flyctl, auth tokens, and automation for launching, scaling, inspecting, and managing distributed workloads.
Yes. With a Fly connection shared to a Space, the agent can check app names, set up health checks, or manage WireGuard peers in a thread.
Fly supports an API key or OAuth; an admin sets one up once when creating the connection and controls which Spaces use it.
Yes. A recurring review of check job status can be turned into a type.com automation that reports to a channel.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect DeepWiki MCP to Claude in type.com to ask questions about any public GitHub repo and read its generated documentation in a thread.
Connect DeployHQ to Claude in type.com to remove stale projects, clear build caches, and manage server groups from a shared thread.
Connect Detrack to Claude in type.com to schedule collections, manage depots, and clear out deliveries from a shared thread.
Connect DEV Community to Claude in type.com to draft articles, look up posts, and check comments or profiles in a shared thread.