Home / Features / Realtime and integrations
Realtime data, webhooks, OAuth connectors, and MCP on osFoundry
Native realtime channels, change-data capture, hosted OAuth, and a fleet of MCP servers — all built into the workspace.
osFoundry is a realtime platform with native data channels, Postgres change-data capture (wal2json-based), inbound and outbound webhooks, an OAuth connector library, and a hosted fleet of Model Context Protocol (MCP) servers. Connect external services in minutes, expose your own APIs to other tools, and stream changes from your app database to subscribed agents in real time.
Quick answer
- Realtime data channels — pub/sub with end-to-end encryption and replay.
- Postgres change-data capture (CDC) using wal2json logical replication.
- Inbound and outbound webhooks with retry, signing, and audit log.
- OAuth connector library — add Slack, Google, Notion, etc. without writing auth code.
- Hosted MCP server fleet — bring tools from Claude Desktop or Cursor, share with your team.
Key capabilities
- Realtime SDK (web + server) with channel-level access control.
- CDC streaming from any per-app Postgres into agents and other apps.
- Hot replay — subscribers can backfill missed events on reconnect.
- Webhook signing (HMAC) and replay-attack protection.
- MCP server management — install, update, share with team or community.
- 30+ pre-built OAuth connectors (Slack, Google Workspace, Notion, GitHub, Linear, Stripe…).
How to do it in osFoundry
- Create a realtime channel — In the app SDK, `channel.publish()` and `channel.subscribe()`. Channel-level access control is configured in the app dashboard.
- Wire CDC from your Postgres — Enable CDC on a table in the database browser. Subscribers (agents or other apps) receive insert/update/delete events as they happen.
- Add an OAuth connector — Open the connector library, pick the service, authorise. Tokens are stored encrypted; refresh handled automatically. Tools become available to agents in scope.
- Install an MCP server — Browse the community catalogue or paste an MCP server config. Tools surface in Maestro and any agent profile that whitelists them.
- Send and receive webhooks — Outbound: configure a destination URL + HMAC secret. Inbound: each app gets a webhook ingest endpoint that signature-verifies and dispatches into your app code.
How osFoundry compares
| Capability | osFoundry | Most other tools |
|---|
| Realtime mechanism | wal2json logical replication + websocket channels. | LISTEN/NOTIFY or third-party SaaS. |
| Replay on reconnect | Built-in hot replay — subscribers backfill missed events. | Manual gap-fill or accept loss. |
| MCP hosting | Workspace-shared MCP fleet — install once, available to all agents. | Per-user local MCP setup (Claude Desktop, Cursor). |
| OAuth | 30+ pre-built connectors with token storage. | Write OAuth flow per service. |
Use cases
- Internal-tools team: CDC streams every CRM update into a Slack channel via a one-line subscribe. Agents react to high-value-deal changes without polling.
- Customer support: Inbound webhook from Zendesk creates an osFoundry agent task. The agent triages, drafts a reply, sends back via the Zendesk OAuth connector.
- AI tools developer: Publish a custom MCP server (e.g. for a niche internal API) to the community catalogue. Other workspaces install and share back improvements.
Frequently asked questions
Is osFoundry’s realtime built on websockets?
Yes — websocket transport with channel-level subscriptions. CDC uses wal2json logical replication for database events; channels use a pub/sub broker.
What’s the latency on a realtime channel?
Within a region, end-to-end p95 is under 200 ms.
Can I use osFoundry as the MCP host for my team?
Yes — install MCP servers once, share them across the workspace. Tools become available in Maestro and to any agent that has them in scope.
How are webhooks billed?
Inbound: per-million ingests at the same rate as serverless function invocations. Outbound: per-thousand deliveries with automatic retry.
Can MCP servers from Claude Desktop be moved here?
Yes — paste the MCP config. The server runs in osFoundry’s fleet and the tools become workspace-shared instead of per-user.
Pricing
Realtime channels and CDC: per-million-message metering. Webhooks: per-million-events. OAuth connectors and MCP server hosting: per-app compute time (containers).
Related features