outreach.io

Create an Outreach app in the Outreach developer portal, then open its API access settings from the API access docs. Configure at least one redirect URI and the OAuth scopes your integration needs. Outreach generates separate development and production client_id/client_secret pairs for the app; note that the secret is shown only once, and production credentials are available after the app is published.

In the Outreach developer portal, add the API Access (S2S) feature to your app as described in Accessing Outreach REST API from server. Select S2S scopes, upload one or more PEM-encoded public keys, and save to receive the app's S2S_GUID. Keep the matching private key on your server; you use that private key plus S2S_GUID to sign a JWT app token, then use that flow to obtain per-installation S2S access tokens. You also need each customer org's INSTALL_ID, obtained via the install setup token or lifecycle webhook flow described in the same doc.

Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.