Hi team,
We're integrating Intercom's MCP server into Fieldwork, an AI agent platform for consumer-brand operators. Our users connect their own Intercom accounts, and the agent calls Intercom tools on their behalf.
Dynamic Client Registration against https://mcp.intercom.com currently returns:
{ "error": "invalid_redirect_uri", "error_description": "Redirect URI https://app.getfieldwork.ai/api/connectors/oauth/callback is not in the allowlist, reach out to Intercom Customer Support if you believe we should support it"}Following the format Seán set out in the earlier thread on this:
- Product or tool name: Fieldwork (https://getfieldwork.ai)
- Exact redirect URI to review: https://app.getfieldwork.ai/api/connectors/oauth/callback
- Production or staging: production (our only environment)
- MCP endpoint targeted: https://mcp.intercom.com
- Use case and distribution model: Fieldwork is a multi-tenant SaaS product. Each end user authorizes their own Intercom workspace through OAuth 2.1 authorization code with PKCE (S256); tokens are encrypted at rest (AES-256-GCM), scoped to the authorizing user, and never shared between users or organizations. The agent reads conversation and contact context, and takes actions in Intercom only when the user explicitly asks. Distribution is direct to our own customers — Intercom appears as one connector in our library, not resold or white-labeled.
We don't have an Intercom workspace of our own to raise a support conversation from, which is why I'm posting here — I saw the community team was able to route a very similar request internally.
Thanks,
Guillaume Dupuy
Fieldwork
guillaume@getfieldwork.ai
