Skip to workspace
Flows

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

Checking

Sign in with Qira to use shared provider keys and models.

Set up AI provider

GitHub OAuth

Checking

Connect through your Qira account. A pasted repository URL never counts as access.

Connect GitHub

Build connectors

OAuth availability and live connection state are separate. Ready requires both.

Replit

Checking

Create or update a Replit app from a checked Flows plan.

Connection status is unavailable right now.

Connection help

Base44

Checking

Send a plan to Base44 while keeping checks and evidence in Flows.

Connection status is unavailable right now.

Connection help

Emergent

Checking

Run a build conversation and bring preview evidence back to Flows.

Connection status is unavailable right now.

Connection help

No connector? Keep moving.

Generate a builder-ready brief, paste it into any tool, then return evidence to Flows for an independent check.

Generate a build brief

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

Use a token issued for this server. Qira encrypts it and sends it only to the endpoint you specify.

Use an API-key header instead

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 clientSetup for Codex, Claude, Cursor, VS Code, and other MCP clients

Access 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.