Give your coding agent the keys to the runway.

FlightStack ships a remote MCP server. Connect it once and your agent reads builds, edits pipelines, and ships releases from the editor.

claude mcp add --transport http flightstack https://api.flightstack.voostack.com/mcp

Streamable HTTP transport. That host is our cloud. Self-hosting? Swap it for your own control plane and everything below is unchanged.

Three steps, one browser prompt

Authentication is OAuth 2.1 with PKCE. No token is ever pasted into a config file.

  1. 1

    Add the server

    One command, or paste the URL into any client that supports remote MCP servers over HTTP.

  2. 2

    Approve once

    The first tool call opens a browser. You sign in, choose a default organization, and approve each scope the client asked for.

  3. 3

    Work from the editor

    The client keeps a refresh token. From then on it reads and drives FlightStack inside whatever you approved.

Scopes

You approve each capability by name

The consent screen shows exactly what a client asked for. Anything it did not ask for stays closed, and the two sensitive scopes are flagged as such.

Headless callers

For anything that cannot open a browser

Cron jobs, CI steps, and scripts send an API key as a bearer token to the same URL. Keys carry the same four MCP scopes plus nine finer REST scopes, so a build-status checker never gets near your signing keys.

A key acts as the person who created it, and stops working when they leave the organization. The value is shown once, at creation.

Open MCP & API Keys ↗ 
# Same endpoint, no sign-in round trip
curl https://api.flightstack.voostack.com/mcp \
  -H "Authorization: Bearer fs_live_..." \
  -H "Content-Type: application/json"

Before you connect it

Which clients work with it?

Claude Code, and any client that can add a remote MCP server over streamable HTTP. There is nothing FlightStack-specific in the transport.

Can I limit it to read-only?

Yes. Approve flightstack:read and nothing else, and the connection can list and inspect but cannot change anything or trigger a build.

What if I belong to several organizations?

The consent screen asks you to pick a default. The connector can still address the others by naming them, inside the scopes you approved.

How do I disconnect it?

Revoke the connection from MCP & API Keys in the app. Refresh tokens stop working immediately, and any API key you issued can be revoked from the same page.

Does this work on a self-hosted install?

Yes. The MCP server is part of the control plane, so it lives at /mcp on whatever host you deployed it to.

Point your agent at it.

Free to start, and the MCP server is on every tier including self-hosted.

Start free API reference