Integrations
Three managed integrations. Exactly three.
OBTO manages Google sign-in, GitHub code sync and Stripe on your own account. Each one below says what it does, which scopes it uses, how you test it and how you rotate it — from the Connectors panel in DevZone, with a receipt for every test. Anything else your agent talks to is a custom MCP tool you build and own; we do not list it here as if it were managed.
Google sign-in · built in
Every OBTO workspace is created and signed in with Google OAuth. It is how a new user gets a workspace with no API key and no password to manage.
Scopesopenid, email, profile
Where it runslogin.obto.co (platform), with the first MCP connection or the sign-up page
TestConnectors → Google → Test records that the platform provides it; there is nothing workspace-specific to configure
RotateNot applicable — no workspace credential is stored
Not a managed connector yet: Google Workspace APIs (Sheets, Gmail, Drive). Your agent can call them through a custom MCP tool with credentials you provide; that is agency work today, not a product connector.
GitHub code sync · per user
Install the OBTO GitHub App, pick repositories, and OBTO syncs their code into an app: frontend modules, pages, stylesheets, and backend files translated into server scripts and routes. Push events on the configured branch keep it current. Export of an OBTO app back to a repository you control is available on request.
ScopesRepository contents (read for sync, write for export), repository metadata (read), push webhooks — all installation-scoped to the repositories you pick
CredentialShort-lived installation tokens minted per call by the GitHub App; nothing long-lived is stored for you to rotate
TestConnectors → GitHub → Test mints an installation token and lists the installation's repositories — a real GitHub round-trip, recorded
Reconnect / revokeSettings → GitHub (connect, choose repositories, disconnect); uninstalling the app on GitHub revokes access at once
Known limits, stated: sync is one-way repository → OBTO today; files over 1 MB are skipped; backend files need the OBTO runtime (routes, data access) to run.
Stripe payments · your account, per workspace
Two things, kept apart. OBTO bills your plan through its own Stripe account. Separately, your apps can take payments on your Stripe account: products, prices, checkout sessions, payment links, subscriptions and webhooks — with your key stored encrypted on your workspace domain only. There is no fallthrough to the operator account: a workspace without its own key gets a refusal, never someone else's Stripe.
ScopesYour secret (sk_) or restricted (rk_) key; your webhook signing secret (whsec_); live mode only when you set allow_live explicitly on your workspace
TestConnectors → Stripe → Test asks Stripe for your balance object using your key (amounts are not recorded) and stores the result as a receipt
RotateConnectors → Stripe → Rotate key: the new key is tested against Stripe first, then stored encrypted; then roll or delete the old key in your Stripe dashboard. The key is never shown again.
Webhook/ms/v2/stripe.bto?tenant=<your domain>, verified with your own signing secret
What is not here. No connector catalog beyond these three. No Slack, Jira, ServiceNow, Postgres or Gmail connectors as managed products — our blog explains how to build those as MCP tools, and that is exactly what they are today: tools you own. When one becomes managed (OAuth, scopes, health, rotation through the panel above) it will be added to this page, not before.
Start free Getting started