Connecting your stack

FoundersOS is the context hub: it knows who the customer is, what the project is, and where the money went. The rest of your stack - chat, code, research, billing, design - plugs in through MCP as the hands that act on that context. This page is not a directory; it’s a way of thinking about how the pieces combine.

The connectors named here are examples of MCP servers that pair well with FoundersOS. They are not official or endorsed integrations - just tools we and others use alongside it. Any spec-compliant MCP connector works the same way.

The mental model

Think of it as context plus hands:

• FoundersOS holds the durable context - customers, contacts, tasks, projects, finances, memory.
• Other connectors do the acting - Slack to notify, GitHub to ship, Claude in Chrome and Kagi to research, Stripe or RevenueCat for revenue, Figma and Canva for design, Resend for email, Sentry for errors.

Your AI reads context from FoundersOS, acts through the other connector, then writes the outcome back to FoundersOS. The loop closes where the work lives.

Pattern: capture, act, remember

The most common shape, and it’s the same across connectors:

1. Capture - a Slack thread or an inbound email becomes a logged interaction on the customer.
2. Act - a follow-up task is created and linked to that customer, maybe assigned to a teammate or to the AI.
3. Remember - the outcome or decision lands in memory so it’s there next time.

Swap Slack for email, or GitHub for a research tool, and the shape holds.

Pattern: playbooks fan out to connectors

A playbook step is either a native FoundersOS task or an external action through a connector. When the connector is present, the step fires for real - create a repo, post to a channel, schedule an event. When it isn’t, the step falls back to a tagged [manual] task so the playbook still completes end to end. That graceful fallback is what lets one playbook run the same whether or not every connector is wired up.

Connectors that pair well

Short read on where each tends to fit (all examples, not official integrations):

• Slack - notifications, digests, and capturing conversations as interactions.
• GitHub - shipping: repos, issues, and release work linked to projects and tasks.
• Supabase - your FoundersOS database itself, plus schema and health checks.
• Vercel - deploys tied to the project you’re shipping.
• Claude in Chrome - research and scraping that a static fetch can’t reach.
• Kagi - fast, high-signal web search to feed research workflows.
• Stripe / RevenueCat - revenue and subscription data alongside the financial tools.
• Figma / Canva - design work that flows into tasks and projects.
• Resend - transactional and outbound email.
• Sentry - error and release monitoring around a ship.

Start small, then snap on more

You don’t need the whole stack on day one. Start with FoundersOS plus the one connector that removes your biggest bit of copy-paste - usually Slack or GitHub - and add the next when a workflow asks for it. The use-case recipes show specific combinations worth copying.