Live and shipping

One URL.
Every AI tool you already have open.

You have five AI tabs open right now. They have never met each other. ChatGPT does not know what you told Claude. Cursor does not know what Perplexity found. You are the only shared memory between them, and that is exhausting.

Connect is the middleware that fixes that. One MCP URL, one API key, paste them once. Your memory and your rules travel with you everywhere.

The actual problem, in full

It is not that the tools are bad at memory. It is that none of them have a shared protocol for knowing who you are. So you re-introduce yourself five times a day. We fixed the seams, not the tools.

Five tabs, five strangers. Every AI tool you open starts fresh. It has no idea what you decided in the last one. Your preferences, your project context, your tone - all of it lives in your head because there was nowhere else to put it. Until now.
Your rules reset at every door. You set your rules in one place. You move to another tool. Gone. The filter you set, the no-fly topics, the way you like things written - each client treats you like a first-time visitor. DreamerOS is the memory that persists between them.

Light does not include an MCP key. DreamWeaver and higher tiers can generate an account-specific MCP connection in the authenticated Connect page.

The live receipt ledger

Which way does the connection travel?

Four connection directions

Know which way
the connection travels.

These paths are separate. Connecting an AI client to DreamerOS does not also authorize DreamerOS to access a third-party account.

The four directions, in full

Use DreamerOS from your AI client. DreamWeaver is an MCP-capable client, such as Claude Desktop, Cursor, or Codex, calling DreamerOS with your account-specific connection details.
Connect a provider to DreamerOS. You authorize OAuth or supply your own provider credential so DreamerOS can call that provider. The gateway stores the connection, not the public website.
Build with DreamerOS. An application uses a documented API or SDK. This is an application integration, separate from your personal MCP client connection.
Receive provider events. A provider sends DreamerOS a webhook. Availability and permissions must be confirmed for the specific provider before it is used.

How do I set it up?

Start in your account

One connection.
Confirm it in your client.

Keep using the tools you have. The authenticated Connect page gives the account-specific path, and the client handshake confirms when it works.

The three setup steps

1. Open authenticated Connect. Eligible accounts can generate an account-specific MCP connection. The page shows only the details for your account.
2. Choose the setup path for your client. Desktop and web clients use provider-specific transports. Connect shows the currently supported instructions rather than assuming the same path works everywhere.
3. Run the client handshake. Only treat the connection as live after the client confirms it. Session continuity, tools, and receipts depend on the active tier, connection, and available runtime capability.

If it speaks MCP, it speaks DreamerOS

Open the authenticated Connect page to see the supported setup for your account and client. Client transport and availability are confirmed there before a connection is used.

Guided desktop setup: Claude Desktop (Anthropic), Cursor (Anysphere), VS Code (Microsoft), Windsurf (Codeium), ChatGPT (OpenAI). Check each in Connect.

Web client setup: Claude.ai (Anthropic), Perplexity (Perplexity AI), Gemini (Google), Grok (xAI). Check each in Connect.

Rotate your key in one click

Self-service key hygiene. If a key leaks, or it is just time for a fresh one, rotation lives behind a single endpoint on the gateway. Old key invalid the moment the new one issues. Every rotation logged to your audit trail.

curl -X POST https://dreameros-scs-gateway-production.up.railway.app/api/v1/me/rotate-key \
  -H 'Authorization: Bearer <your gateway JWT>'

# Response (200 OK)
{
  "api_key": "dros_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "rotated": true,
  "note": "Save this key now. The previous key is no longer valid..."
}

Built in - audit trail by default. Every rotation emits an integrity event: who, when, what surface (self-service vs auto-rotation policy). Append-only, queryable from the audit log.
Available now - self-service for everyone. Any authenticated DreamerOS user can rotate their own MCP key. No support ticket. No HC intervention. Light, Pro, Elite all included.
Roadmap - multi-surface propagation. Coming next: rotate once, DreamerOS pushes the new key to every connected client (Claude Desktop, Perplexity, Railway env, Vercel env) automatically. 24h grace window so nothing in flight drops.

Rotate your key now See the Pro API surface

What can it connect to?

Works with your stack

One connection.
Your whole stack.

Choose a setup path for an MCP client or a provider connection. The authenticated Connect page confirms what your account can use before you authorize access.

A listed provider is not proof that a customer credential is configured or healthy. Connect confirms the applicable path in your account.

The connector catalog, by category

Code & Build. Your editors, agents, and infra. One MCP URL across all of them.

Bring Your Own Model. Vendor-agnostic. Plug any model in. Any OpenAI-compatible endpoint works.

Comms & Inbox. Email and team chat. Checked before anything sends.

Plan & Track. Projects, docs, calendars. Memory carries across every one.

Reach & Audience. Publish and engage. Every post runs an intent gate first.

Data & Web. Pull the web and your files into checked, sourced answers.

Firecrawl (Connect now)
Resend (Connect now)
Google Drive (Coming soon)

Money & Commerce. Billing and storefronts. Checked before money moves.

Stripe (Coming soon)
QuickBooks (Coming soon)
Etsy (Coming soon)

Create & Media. Design, video, voice. Your description is sharpened before it generates.

Setup paths are listed above. Account availability is confirmed in Connect.

Provider connection directions

Understand the path. Confirm the live connection. DreamerOS can expose provider setup paths for tools such as Railway, GitHub, Vercel, Slack, Notion, Linear, Gmail, and Stripe. Check availability for each in Connect.

Each outbound integration means one fewer manual step between "approved" and "shipped." We are wiring them in the order they actually matter.

Confirm availability in Connect

Which promises are proven?

The ledger

Every promise on this page,
tracked in the open.

A promise is only called customer-ready when the evidence holds up end to end. This ledger lists each public Connect and DreamWeaver promise, its current state, and the next check it must pass. It updates when the evidence does, not when the copy does.

The ledger, row by row

Promise	State	Next check
DreamWeaver and higher tiers can obtain an account-specific MCP connection. `gateway/app/api_key_endpoint.py` `GET /api/v1/actions/api-key`	Being proven	Run an authenticated customer setup and retain a public-safe receipt that proves the desktop client completed a handshake.
People can find the authenticated desktop setup for Claude Desktop, Cursor, and Codex Desktop. `dreameros-app-frontend/src/app/connect/desktop/page.tsx` `dreameros-app-frontend/src/components/connect/ManualConnectionsSection.tsx` `dreameros-app-site/connect-setup.php redirects to authenticated /connect/desktop`	Being proven	Capture an HC-approved screenshot of the account-specific desktop setup and run one live client handshake.
A user can authorize or provide a provider credential so DreamerOS can call that provider. `gateway/app/routes_integrations.py` `gateway/app/connection_store.py`	Being proven	Verify encryption is configured in the target runtime and complete a provider-specific OAuth or key flow with a customer-safe receipt.
An existing AI client can use DreamerOS without replacing the user's workflow. `gateway/app/mcp_server.py` `gateway/app/api_key_endpoint.py`	Being proven	Prove one supported setup per named client through a live tool listing or handshake and record the exact client transport.
Available checks and receipts appear in the user's live session. `gateway/app/api_receipts.py` `dreameros-app-frontend/src/components/GovernanceRibbon.tsx`	Being proven	Verify a customer session with the intended tier and preserve a public-safe evidence capture. Do not claim universal per-turn receipts.
A service that supports MCP can call DreamerOS with a user's account-specific connection. `gateway/app/mcp_server.py` `gateway/app/mcp_auth.py`	Being proven	Run a bounded Zapier-specific MCP handshake and publish a customer-safe setup receipt.
DreamerOS can automate a customer's Zapier-connected applications. `gateway/app/routes_zapier.py`	Being proven	Build per-customer credential isolation, entitlement, onboarding, live execution evidence, and failure receipts. The current route uses a shared operator credential.
A customer application can build against a documented DreamerOS API or SDK.	Being proven	Publish the vendor-neutral connection contract, authentication model, supported endpoints, SDK policy, and live integration proof before marketing this as customer-ready.
Small tasks use local capacity first and appropriate work can offload through DreamerOS Live. `governance/00_CORE/DREAMEROS_GATEWAY_OFFLOAD_LANE_v1_0_0.md` `governance/proposed/AGENT_OFFLOAD_SALES_MODEL_v1_0_0.md`	Being proven	Build customer entitlements, credit accounting, provider routing, receipts, fallback, and a customer-visible usage surface.

The live receipt ledger

What does my tier get?

What your tier gets you

Your account decides.
Connect confirms it live.

Light does not include an MCP key. DreamWeaver and higher tiers can generate an account-specific MCP connection in the authenticated Connect page. Provider access is confirmed there before you connect.

The tier table, in full

Tier	Web paste flows	MCP API key	Outbound automation
Light (free)	Yes	No	No
DreamWeaver	Yes	Yes	No
Pro (recommended)	Yes	Yes	Provider-specific
Elite	Yes	Yes	Provider-specific

Light. Free to start. Light does not include an MCP key. The authenticated Connect page shows the available upgrade path for your account.
DreamWeaver. Can generate an account-specific MCP connection in Connect. The live page confirms the client setup and any provider access for your account.
Pro. Includes an MCP connection. The authenticated Connect page confirms the available client setup and provider actions before access is authorized.
Elite. Includes an MCP connection and account-specific setup. The authenticated Connect page confirms the actions and providers available to the account.

Two emails, one canonical you

Most people end up with more than one email tied to AI accounts over time. DreamerOS links them. Sign in with either one - your memory, tier, and connected clients resolve to the same canonical account every time.

curl https://dreameros-scs-gateway-production.up.railway.app/api/v1/me/aliases \
  -H 'Authorization: Bearer <your gateway JWT>'

# Response (200 OK)
{
  "canonical_user_id": "4942291b-...",
  "canonical_email": "you@example.com",
  "aliases": [
    {
      "alias_email": "you-old@example.com",
      "linked_at": "2026-05-19T...",
      "note": "HC alias merge"
    }
  ]
}

How it resolves - one-hop only. Each alias points to exactly one canonical account. No chains, no loops. The resolver runs on every authenticated request, so a sign-in via either email lands the same canonical state.
What stays put - history keeps its attribution. Rows written under the alias id stay tagged with the alias. The resolver unifies at read time. No silent backfill. The audit trail bifurcates by design and unifies on lookup.
Roadmap - self-service linking. Today merges happen via the admin endpoint. Self-service alias linking from the user surface needs a verified-email round trip; that ships in a follow-on. The read endpoint is live now.

More ways in

Start with your account. Confirm the connection in your client. Eligible accounts can generate one account-specific MCP connection. The authenticated page and client handshake show what is available now.

See Automate See Pro

Open Connect

One URL. Every AI tool you already have open