Connector Platform
Give your agent a single MCP surface to orchestrate 100+ SaaS connectors per end user while you ship a multi-tenant builder app.
Overview
Connector Platform is an MCP server for the Build phase that routes agent tool calls through 100+ SaaS integrations scoped per end_user for multi-tenant apps.
What is this MCP server?
- 100+ pre-built SaaS integrations for builder applications
- Multi-tenant model with connections scoped per end_user
- Remote streamable-http MCP at connector-mcp…/mcp/{builder_id}/self
- Builder PAT (cpt_*) plus builder UUID for auth
- Open-source plugin repo on GitHub (connector-platform-plugin)
- 100+ pre-built SaaS integrations (catalog claim)
- Server version 0.1.0
- Transport: streamable-http remote MCP
What problem does it solve?
Shipping a SaaS with dozens of third-party connections means endless OAuth variants and tenant isolation logic that agents cannot safely invent on the fly.
Who is it for?
Indie SaaS founders building agent-native or automation-heavy products who need many integrations with tenant boundaries from day one.
Skip if: Hackathons that need one public API with no end-user accounts, or teams that refuse hosted PAT-based remote MCP.
What do I get? / Deliverables
After you register the remote MCP with PAT and builder_id, your agent can drive pre-built connectors under per-user scopes instead of one-off integration code per vendor.
- Remote MCP endpoint wired to your builder tenant
- Agent-accessible calls across the platform’s SaaS connector set
- Per end_user scoped integration actions in dev or staging
Recommended MCP Servers
Journey fit
How it compares
Multi-tenant SaaS integration MCP platform, not a single-service MCP or local-only devtool skill.
Common Questions / FAQ
Who is Connector Platform for?
Builder-first SaaS authors who want agents to manage or invoke many third-party apps for each signed-in customer without maintaining 100 separate MCP servers.
When should I use Connector Platform?
Use it in Build while you implement your product’s integration layer, provision builders in the portal, and test agent workflows against real end_user scopes.
How do I add Connector Platform to my agent?
Create a builder in the Connector Portal, copy your cpt_* PAT and builder UUID, then add the streamable-http remote MCP URL with Authorization Bearer {token} in your agent’s MCP settings.