docs: add Outreach MCP server setup page - #505
Draft
leet-c1 wants to merge 2 commits into
Draft
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Adds the customer-facing setup guide for the Outreach MCP server and registers it in the nav. Outreach uses per-user OAuth, so the page follows the single-auth-method shape rather than the tabbed layout used for MCP servers that also accept a shared token. It covers creating an app in the Outreach Development Portal, setting the redirect URI, selecting scopes, registering the server, and rotating or revoking credentials. The scopes section carries the two behaviors that cause most failed authorizations, both of which produce the same unhelpful vendor error: - Outreach rejects the entire authorization if any one requested scope is not selected on the app, and names no scope in the message. - `all` is a distinct scope string, not a shorthand. Selecting read, write and delete does not make `<record>.all` grantable. The default and optional scope lists match the scopes the Outreach MCP server requests, split by permission so the write and delete tiers are clearly opt-in. mint broken-links: no findings for this page, no parse errors.
leet-c1
force-pushed
the
leet/mcp-server-outreach
branch
from
August 24, 2026 19:13
1b4b081 to
bbed53d
Compare
The all-or-nothing rejection was documented only in the scopes section, after the step it should guard. A reader working straight through the setup steps could finish app creation with a partial scope selection and then hit an error that names no scope. Adds one sentence to the scope-selection step itself, linking to the fuller explanation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the customer-facing setup guide for the Outreach MCP server and registers it in the nav.
Outreach uses per-user OAuth only, so the page follows the single-auth-method shape rather than the tabbed layout used for MCP servers that also accept a shared token. Closest siblings are the PagerDuty and Slack pages — PagerDuty for structure, Slack for the required/optional scope tiers.
Contents
Creating an app in the Outreach Development Portal, setting the redirect URI, selecting scopes, registering the server in C1, how credentials are shared, tool discovery and governance, and rotating or revoking credentials.
Why the scopes section is the long one
Outreach has two scope behaviors that produce most failed authorizations, and both surface as the same unhelpful vendor error with no indication of the cause:
allis a distinct scope string, not a shorthand. Selectingread,write, anddeletefor a record type does not make<record>.allgrantable.Both are documented up front, with a FAQ entry for the error message so a customer hitting it can self-serve. The default and optional scope lists match the scopes the Outreach MCP server actually requests, split by permission, so the write and delete tiers read as clearly opt-in.
Draft — do not merge yet
The scope tiers on this page match a pending change to the scopes the Outreach MCP server requests. That change is itself still in draft, pending confirmation of how the vendor's scope picker presents permissions. Merging this page first would publish setup instructions for a scope set the server does not yet request.
Ready to un-draft once the scope change lands.
Checks
mint broken-links: no findings for this page, no parse errors. The 8 broken links it reports are pre-existing onmaininbaton/sendgrid,baton/twilio-segment-v2,connector-template, andindex— untouched by this branch.