Initiate OAuth authorization flows for your audience. Requires an OAuth app registered in the MewCP dashboard first.
Start OAuth flow for an audience member
Generates an authorization URL to redirect your audience member to. After the user
authorizes, MewCP stores the credential under their externalUserId.
Prerequisites:
- Register an OAuth app for the provider and assign it to the server key you'll use: Dashboard (mode=business) -> Servers -> select server -> Register OAuth Client.
- Requires the
x-mewcp-keyheader (see Authentication above): the OAuth app used is always the one assigned to that server key, there is no per-request app selection.
After success, subsequent MCP proxy calls include x-external-user-id: {externalUserId}
in the request headers and MewCP resolves the right credential automatically.
path Parameters
providerProvider slug (e.g. Google, github, Slack, notion)
Headers
x-mewcp-keyAPI Key of the business-mode server to connect this user to. Must match provider.
Start OAuth flow for an audience member › Request Body
externalUserIdYour internal user identifier. Used to associate the credential with your user.
frontendCallbackUrlURL to redirect the user to after OAuth completes (receives ?provider=github&success=true)
Optional metadata about the audience member. Stored alongside their credentials for display in the MewCP dashboard.
Start OAuth flow for an audience member › Responses
Authorization URL ready. Redirect your user to authUrl.
authUrlRedirect your audience member to this URL
stateCSRF state token (managed internally, no action needed)