Connected Apps is a newer, provider-gated feature. It requires the Composio integration to be configured. On self-hosted deployments, set
COMPOSIO_API_KEY. When it is absent, the provider registry is still wired: the gallery still loads and lists Composio as an unconfigured provider (with a setup hint), but connecting an app, listing its tools, and other per-app actions return 503 until the key is configured.Overview
Connected Apps let you OAuth into third-party SaaS apps, via Composio, which brokers 250+ apps, and expose them to your agents as managed MCP servers. The key benefit: you don’t hand-configure an MCP URL or headers. Connecting an app auto-registers a managed MCP server that your agents can attach to. Orca (through Composio) holds the credentials and manages the connection for you.Flow
1
Browse the gallery
Open the app gallery and pick a SaaS app to connect.
2
Connect (OAuth)
Click Connect. The OAuth flow opens in a new browser tab and takes you
through the provider’s consent screen. (It intentionally does not use a
popup window, since some browsers suppress WebAuthn/2FA prompts inside
popups.) The connection begins in an INITIATED state.
3
Connection goes ACTIVE
Once OAuth completes, the connection flips to ACTIVE.
4
Managed MCP server appears
A managed MCP server for that app is auto-registered. It shows up
alongside your other MCP servers, and agents can attach to it: no URL or
header configuration required.
Connection status
Managing connections
From the dashboard you can:- See each connection’s status (
ACTIVE/INITIATED/FAILED/EXPIRED). - See which agents have access to a connected app.
- Disconnect an app, which revokes the connection and its managed MCP server.
Because Composio manages the credentials for connected apps, you typically don’t need to store their tokens yourself. For MCP servers you configure by hand, put credentials in Secrets and reference them as
secret:// in the headers.Related
MCP Integration
How agents consume MCP servers.
Secrets
Credentials for hand-configured MCP servers.