Flightcontrol (BYOK)

Flightcontrol (BYOK) — connector documentation

• MCP endpoint: https://byok-flightcontrol.connectorbay.com/mcp
• REST API: POST https://byok-flightcontrol.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-flightcontrol.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Flightcontrol Flightcontrol API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-flightcontrol.connectorbay.com/health · Tool schemas: https://byok-flightcontrol.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-flightcontrol · agent@connectorbay.com

What Flightcontrol (BYOK) is for

Flightcontrol (BYOK) lets an AI assistant read your own Flightcontrol data through the Flightcontrol API with a key you supply (Flightcontrol API key). Read-only: 11 tools (list_projects, get_aws_account, list_services, get_service, get_service_scaling, get_deployment, get_job_execution, list_service_domain_groups, get_domain_group, list_group_domains, get_domain). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.flightcontrol.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Flightcontrol. Flightcontrol and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which projects exist in my Flightcontrol account?"
• "Is my AWS account connected to Flightcontrol?"
• "List the web services in my Flightcontrol project"
• "Where are the logs of my Flightcontrol web service?"
• "How many instances is my Flightcontrol service running?"
• "What is the status of Flightcontrol deployment clcpcxekt000lc9ojqtgtc26y?"

What it does

• list_projects: List all projects owned by the team: id, name and the linked Git repository URL.
• get_aws_account: Get one connected AWS account: Flightcontrol id, your own given id, the 12-digit AWS account number, display name and connection status.
• list_services: List services (web, worker, database, cache and so on) with project and environment ids, filtered by project, environment or type. Paged with skip and take.
• get_service: Get one service by id: name, type, project, environment and where its runtime logs live (CloudWatch log group).
• get_service_scaling: Get a service's current, desired, running and pending instance counts and its autoscaling minimum and maximum.
• get_deployment: Get one deployment: status, Git branch and commit, environment, and the status of each service deployment inside it.
• get_job_execution: Get the status of one scheduled-job execution: status, start, finish time, exit code and error.
• list_service_domain_groups: List the custom-domain certificate groups of a service with status, CloudFront distribution id and certificate status.
• get_domain_group: Get one domain certificate group: status, CloudFront distribution id and certificate status.
• list_group_domains: List the domains attached to a certificate group with attachment status, type and the DNS records to create.
• get_domain: Get one domain: attachment status, type and DNS records with their propagation status.

BYOK key

You bring your own Flightcontrol Flightcontrol API key (https://app.flightcontrol.dev/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.flightcontrol.dev over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://www.flightcontrol.dev/docs/reference/http-api (the API this connector calls, with a BYOK key)

Live from the Flightcontrol API (api.flightcontrol.dev) with a BYOK key; documentation: https://www.flightcontrol.dev/docs/reference/http-api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Flightcontrol. Flightcontrol and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Flightcontrol account.

Built for: Worldwide. Languages: English.

Flightcontrol (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Flightcontrol (BYOK) is. Flightcontrol (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Flightcontrol data: Read your Flightcontrol projects, services, scaling, deployments, custom domains and AWS account links with your own organization API key. You bring your own Flightcontrol Flightcontrol API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Flightcontrol call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.flightcontrol.dev, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Flightcontrol rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Flightcontrol receives. The request we make on your behalf, including the key and the arguments, under Flightcontrol's own terms and privacy policy. Flightcontrol acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Flightcontrol gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Flightcontrol data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Flightcontrol (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Flightcontrol at any time to end all access.

Children. Flightcontrol (BYOK) is a general-audience service operated by the adult using the assistant, under Flightcontrol's own age rules.

Changes. We will post changes here with a new effective date.

Flightcontrol (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Flightcontrol (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Flightcontrol (BYOK) provides: Read your Flightcontrol projects, services, scaling, deployments, custom domains and AWS account links with your own organization API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Flightcontrol credentials and only access data you are allowed to access. Flightcontrol's terms apply to your use of Flightcontrol; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Flightcontrol. Flightcontrol and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Flightcontrol returns, lightly trimmed; it may be incomplete, delayed or changed by Flightcontrol. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Flightcontrol account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Flightcontrol's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Flightcontrol may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Flightcontrol key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Flightcontrol takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-flightcontrol

Flightcontrol (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-flightcontrol.connectorbay.com/mcp
• REST API: https://byok-flightcontrol.connectorbay.com/openapi.json
• Live status: https://byok-flightcontrol.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Flightcontrol (BYOK) never asks for them.