Integrations Overview

Cofounder integrations let agents work with the tools your company already uses.

Add integrations from Integrations when you want agents to access more of your company stack.

Product And Engineering Context

Cofounder works best when it understands the product you are building elsewhere. Engineering integrations can provide that context and support handoffs:

GitHub for connected repository context, pull requests, reviews, and marketing-site code changes
Linear for product plans, issues, and engineering handoffs
observability and analytics tools for product signals that should inform growth, support, and operations

Connecting an engineering tool does not transfer ownership of the core product to Cofounder. Keep building the main application, database, authentication, and hosting stack in your preferred engineering workflow. Cofounder can turn company work into a specification or prompt for that workflow, then use the result as context for the rest of the business.

Native Integrations

Native integrations are first-party Cofounder connections with product-aware agent tools, approvals, and runtime handling.

Cofounder supports native integrations across these areas:

Area	Native integrations
Engineering and delivery	GitHub, Vercel, Supabase, Linear, LaunchDarkly, Sentry, PagerDuty, Logfire, Datadog, Neon, Railway, Render
Communication and support	Gmail, Google Calendar, Slack, Intercom, AgentMail
Docs, files, and knowledge	Notion, Google Docs, Google Drive, Google Slides, Airtable, Granola, Limitless
Revenue and operations	Ramp, Loops, Metabase, Attio
Marketing and publishing	PostHog, Google Search Console, Postiz, Social Publishing, Layers, Figma
Research and enrichment	Web, PhantomBuster, People Data Labs, enrichment, research workflows, stock market, weather
Media and generation	Image generation, Canvas Video Studio, Agent Media, OpenRouter Video, video post-processing, Kimi
Developer agents and infrastructure	Codex, Claude Code, Devin, Doppler SecretOps, Composio, Zernio

Availability can vary by workspace, plan, and connected account. The Integrations page is the source of truth for what is connected in your workspace and which agents can use each connection.

Examples

Linear lets Cofounder start or continue work from issues, route engineering tasks, and accept assigned Linear work as Cofounder tasks. See Linear.
Ramp supports operations workflows such as the Roadmap's agent-guided Incorporate LLC node.
Notion lets agents read pages and update existing pages in place when the task calls for changing a shared doc.
Granola lets agents list folders and notes, fetch meeting summaries, and include transcripts when exact wording matters.

For payments, use the dedicated Payments And Stripe guide.

MCP Servers

Custom MCP servers let a workspace bring its own MCP-compatible tools into Cofounder, then choose which agents can use them.

Use custom MCP servers when:

your team already has an MCP server for an internal system, private API, or specialized toolchain
the tool should be available to agents through the MCP protocol rather than a native Cofounder product workflow
you need per-agent access control over which custom tools an agent can call
the server's tools can run safely inside agent tasks and sandboxed workflows

A typical custom MCP setup looks like this:

Open Integrations and go to MCP.
Add or paste an mcp.json configuration with an mcpServers object.
Save the configuration so Cofounder parses the servers and shows each saved MCP server.
Keep the servers that should be available marked as enabled.
Use Agent access to choose which agents can use each saved MCP server.
Ask the relevant agent to use the server's tools in a task. Exposed tools appear to agents as MCP-backed tool names such as mcp_<server>_*.

Use native integrations when Cofounder has a purpose-built workflow for the service. Use custom MCP servers when you need to bring your own MCP tool surface into the agent runtime.