Managed Providers
Connect the reviewed hosted MCP providers shipped in the Oblive catalog.
Managed integrations are reconciled from a reviewed Git catalog. Provider name, documentation, setup guidance, categories, profile grants, authentication contract, and tool policy are catalog owned. Your organization owns connection state, credentials, access mode, and selected tools.
Shipped Providers
| Provider | Primary Use | Default Profile Grants | Credential |
|---|---|---|---|
| Resend | Transactional email | Growth, Support | API key |
| Instantly | Outreach operations | Growth | API key |
| Exa | Web research and extraction | Growth | API key |
| Firecrawl | Search, scrape, map, and extraction | Growth | API key |
| Stripe | Payment and customer evidence | Growth, Support | Restricted API key |
| GitHub | Repository work | Engineering | Personal access token |
| Apollo | Lead and company research | Operator, Growth | Provider authorization |
| PostHog | Product and behavioral analytics | Operator, Growth, Engineering | Project personal API key |
Connect a Provider
- Open the organization’s Integrations page.
- Select the provider and read its setup instructions.
- Create the narrowest provider credential that supports the intended work.
- Choose read-only or full access.
- Narrow the enabled tools when the provider supports tool selection.
- Connect and allow Oblive to validate credentials and discover eligible tools.
- Confirm the integration reports ready before assigning work that depends on it.
Provider Notes
GitHub
Read-only mode uses GitHub’s provider-enforced read-only endpoint. Repository access and token scope remain owned by the connected GitHub identity.
Stripe
Use a restricted key with the minimum permissions. OAuth installation is not part of the current managed Stripe integration.
Exa and Firecrawl
Only reviewed tools are exposed. Newly added provider tools are not enabled automatically. Long server-side research is bounded by the configured tool timeout.
Apollo
Apollo uses provider authorization rather than an API key. Read-only mode requests profile and people-search access. Full mode adds the reviewed people and company matching, enrichment, job posting, and result-reading scopes; it does not include contact mutation, CRM, lists, sequences, email, tasks, or purchasing. Some full-mode operations consume Apollo credits.
Do not use data obtained through Apollo MCP to train machine-learning models. Production Oblive deployments should complete Apollo’s MCP partnership registration before offering the integration to customers.
PostHog
Create a project-scoped personal API key with PostHog’s MCP Server preset. Oblive forces tools mode and limits the server to events, data schema, insights, dashboards, SQL, and persons. Read-only mode also asks PostHog to enforce a read-only session.
Rotate or Disconnect
Credential changes invalidate reusable authorization state. After rotation, verify readiness and run a bounded read before resuming consequential workflows. Disconnect an account before attempting to replace it with a different identity when the provider requires identity continuity.
Developers adding a provider should follow Add a Managed MCP.