integration plan
open-connector — the auth gateway plan
The plan for coworker SaaS access runs through
oomol-lab/open-connector — an open-source auth
gateway connecting 1000+ SaaS providers to AI agents — so that coworkers reach QuickBooks (finance
coworker), DocuSign (legal coworker), and Atlassian (product-management coworker,
opencoworkers.atlassian.net) through one inspectable gateway instead of per-coworker credential
sprawl. See /team for which coworker owns which SaaS duty.
Access paths
One gateway, five ways in — the same provider ids, Action ids, schemas, and contracts across all of them:
| path | used from |
|---|---|
| Connector SDK | app code — the coworkers TypeScript packages call Actions directly |
oo CLI | the local-agent relay — coworker sessions on the operator's Mac relay through it |
| MCP | agent hosts — Claude/Cowork sessions consume connectors as MCP tools |
| HTTP / OpenAPI | custom clients — anything that can speak REST against the gateway |
| Web Console | administration and debugging — humans inspecting what agents did |
Why a gateway
- Inspectable runtime: credentials, scopes, schemas, policies, and run logs all live inside the gateway's runtime where they can be audited — never scattered across coworker containers.
- Deployment freedom: runs locally, on Fly.io, on Cloudflare-compatible infrastructure, or through OOMOL's hosted runtime — the contract stays identical across open-source and commercial SaaS deployments.
- Coworker fit: the finance coworker's QuickBooks duty, the legal coworker's DocuSign duty, and the
product-management coworker's Atlassian duty (all recorded verbatim in
opencoworkers-team.json) each become gateway providers with scoped credentials, not secrets pasted into prompts.
Honest scope note: this is a planned integration. No open-connector instance
is deployed for this platform yet, no provider credentials are wired, and nothing on this site talks to the
gateway — this page records the plan (from the operator directive at
organizations/operator-prompts/2026-07-17-coworkers-refactor-apple-containers.json) so the
build has a durable target, not a claim that it already exists.