OAuth, API key, bearer — any auth. Point us at the official documentation; we extract, generate the manifest, validate, and publish. Ready to consume via MCP, REST, or plugin.
No credit card. Hello world in 30 seconds.
/connector-platform add followed by the service.$ claude /connector-platform add githubPersonal modeYou just pass the name or URL of the service — the rest is automatic.
connect-session from your backend.$ curl -X POST api.cp.dev/connect-sessionMulti-tenant modeWhitelabel + per-end-user Postgres RLS.
Generic by design: works for both Personal and Multi-tenant modes. What changes is where the token lives — you never touch YAML, OpenAPI specs, or JSONata.
Our docs reader extracts the API, the AI generates the YAML manifest, automated validations run (reachability, schema, critic), and our team reviews before publishing. You consume — you don't write adapters.
Refresh, revocation, per-tool scopes, per-user isolation. You'll never write “store the refresh token securely” again.
MCP server, REST API, and plugins (Claude Code, Cursor, or the agent you build) — all pointing at the same audit log. The client changes — the contract doesn't.
Three pillars where we make a real difference, three where we disappear behind your product.
BYO OAuth: register your own app on GitHub/Slack/etc — your users authorize your name, not ours. Client secret never touches the browser.
Postgres RLS by user_id + tenant_id. One client's token never sees another's data — not by convention, by database policy.
Every tool call is logged with request_id, effective OAuth scope, and end user. Exportable to Datadog/Splunk via webhook.
MCP server, REST API, and IDE/agent plugins (Claude Code, Cursor, or your own) all come from the same published connector. You don't pick — you expose all three and let the client decide.
Same bearer for everything. Per-scope rotation, configurable expiry, instant revoke via API or dashboard.
Consent screen on your domain, with your logo and your colors. Your users never see our wordmark — unless you want them to.
The client changes — the contract doesn't. cpt_* token works in all three.
# You point at the official docs — we extract, generate the manifest, validate, and publish.
$ curl -X POST https://api.connector-platform.dev/v1/connectors/request \
-H "Authorization: Bearer cpt_live_8f3c…a91" \
-d '{"docs_url": "https://docs.github.com/rest", "slug": "github", "category": "vcs"}'
{
"status": "queued",
"estimated_review": "2–4 business days",
"request_id": "req_01HZ9F…"
}
# You don't write YAML, OpenAPI specs, or JSONata. You get the connector ready to use.# claude_desktop_config.json — add the MCP server
"mcpServers": {
"github": {
"url": "https://mcp.cp.dev/v1/github",
"headers": {
"Authorization": "Bearer cpt_live_8f3c…a91"
}
}
}
# 12 tools registered: list_repos, create_pr, comment_issue, …# Same token. Same audit log. Pure JSON response.
$ curl https://api.cp.dev/v1/github/list_repos \
-H "Authorization: Bearer cpt_live_8f3c…a91" \
-H "X-User-Id: usr_alice"
{
"data": [
{ "name": "connector-platform", "stars": 1284 },
{ "name": "manifest-spec", "stars": 312 }
],
"request_id": "req_01HZ9F…"
}# Inside Claude Code — the plugin discovers, authorizes, registers.
$ claude /connector-platform add github
→ Opening GitHub OAuth in the browser…
→ Authorized as @daniel
→ 12 tools registered
$ claude "List the 5 open PRs in connector-platform"
# tool: github.list_pull_requests (audit_id req_01HZ9F…)Off our tech-debt list. In 2 days we replaced 3 homegrown OAuth integrations with Connector Platform — kept the audit log compatible with our SOC.
// stats and quote: placeholders, to be wired up with real data before GA.
You pay per tool call that reaches the upstream. OAuth handshakes, internal retries, and the audit log are on us.
Private beta, no credit card. You walk away with a cpt_* token and twelve ready-made connectors.