Codex
Add a custom MCP in Settings → Plugins → MCPs. Choose Streamable HTTP, enter the Qira URL, and supply the access token in the bearer-token field when needed.
One Qira account · connected tools
Bring Flows into an AI client, or bring another platform’s tools into Qira. Both use MCP, the shared protocol supported by a growing range of AI tools.
Open your connectionsAdd a remote MCP server with Streamable HTTP transport:
https://flows.oortstack.com/api/mcp
Public access provides real flow search, full step instructions, and validation guidance. To use your connected platforms from the client, create an access token in Connections and set its Authorization header to Bearer YOUR_QIRA_ACCESS_TOKEN. Your provider credentials stay in Qira.
Add a custom MCP in Settings → Plugins → MCPs. Choose Streamable HTTP, enter the Qira URL, and supply the access token in the bearer-token field when needed.
claude mcp add --transport http qira https://flows.oortstack.com/api/mcp
Use /mcp to check the server. Configure a bearer header using Claude’s secret-management guidance to access connected platforms.
{
"mcpServers": {
"qira": {
"url": "https://flows.oortstack.com/api/mcp"
}
}
}Use your client’s secret settings for the Authorization header. The exact configuration file differs by client.
{
"servers": {
"qira": {
"type": "http",
"url": "https://flows.oortstack.com/api/mcp"
}
}
}Add to your MCP configuration. Configure a secret input for Authorization when using connected platforms.
For Claude Desktop or another stdio-only client, download the Qira bridge and run it with Node.js 18 or later. Set FLOWS_MCP_AUTH to your Qira access token in your client’s environment settings.
{
"mcpServers": {
"qira": {
"command": "node",
"args": [
"/absolute/path/to/qira-mcp-bridge.mjs"
]
}
}
}Client support, account plans, and organization policies vary. A client that requires an OAuth-only remote server cannot use Qira’s bearer-token connection yet. Importing this configuration is not proof of a successful connection; confirm that tools appear in the client.
GitHub connects through your Qira account. Replit requires provider sign-in and consent. Direct Base44 and Emergent sign-in is waiting for provider approval; use the options below in the meantime. Platforms without a public API or MCP interface can use an exported Flows brief and return evidence through the supported run workflow.
Protocol and client references: MCP remote servers, Claude Code, Cursor, VS Code.
Direct Base44 sign-in from Qira needs Base44 to approve our callback. You can keep working with a brief, or use the two MCP servers in an AI client that supports Base44’s sign-in.
https://app.base44.com/mcp. Complete Base44’s own sign-in and consent in that client.Base44 account and plan requirements apply. Adding Base44 to your AI client does not connect it to your Qira account or transfer credentials between them.
Emergent’s provider registration is blocking direct Qira sign-in. Create an Emergent brief, paste it into your project, then bring the requested preview and evidence back to your Flows run.
Connect Replit and complete Replit’s sign-in and consent. If your provider account cannot authorize this connection, use a Replit brief and return the evidence to Flows.