Skip to content
Flows

One Qira account · connected tools

Use Qira wherever you build

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 connections

Connect an AI client to Qira

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

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.

Claude Code

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.

Cursor and other JSON-configured clients

{
  "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.

VS Code

{
  "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.

Connect another platform to Qira

  1. Sign in with your Qira account and open Connections.
  2. Use the built-in provider’s sign-in button, or add its public HTTPS MCP endpoint and an optional provider-issued bearer token.
  3. Qira initializes the MCP session and discovers the actual tool catalog. A successful discovery saves your encrypted connection.
  4. Select a tool, inspect its input schema, and run it with explicit JSON arguments. Your AI client can use the same connection with your Qira access token.

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.

Use Flows with Base44

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.

  1. Create a Base44 brief in Flows and copy it into your Base44 project.
  2. Build in Base44, then return to the same Flows run with the preview, commit, or test output it requests.
  3. For an AI client workflow, add Qira using the instructions above and add Base44’s remote MCP server separately: 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.

Use Flows with Emergent

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.

Use Flows with Replit

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.