Connect once · verify live
Connections
Your Qira account keeps your connections and keys together. Flows checks each connection again before a build can claim it is ready.
Account connections
Identity, model access, and repository access.
Checking live status…
AI providers
CheckingSign in with Qira to use shared provider keys and models.
GitHub OAuth
CheckingConnect through your Qira account. A pasted repository URL never counts as access.
Build connectors
OAuth availability and live connection state are separate. Ready requires both.
Replit
CheckingCreate or update a Replit app from a checked Flows plan.
Connection status is unavailable right now.
Base44
CheckingSend a plan to Base44 while keeping checks and evidence in Flows.
Connection status is unavailable right now.
Emergent
CheckingRun a build conversation and bring preview evidence back to Flows.
Connection status is unavailable right now.
No connector? Keep moving.
Generate a builder-ready brief, paste it into any tool, then return evidence to Flows for an independent check.
Connect another platform
Use the built-in options above first. For another platform, add its MCP server here. Qira checks its available tools before saving it.
Add a platform with MCP
Bring Qira into your AI tools
Connect an MCP-compatible client to https://flows.oortstack.com/api/mcp. Search and read public flows immediately. A Qira access token also lets your client use the platforms you connected here.
Set up an AI client
Setup for Codex, Claude, Cursor, VS Code, and other MCP clientsAccess tokens expire after 90 days. Each new token replaces the previous one. A token gives its holder access to your connected tools; keep it in your client’s secret settings.