Skip to main content

Overview

Barndoor connects users to your MCP server using the OAuth 2.0 authorization code flow. When a user authorizes Barndoor, your platform redirects their browser to a Barndoor-hosted callback URL with the authorization code. For that redirect to succeed, the callback URL must be registered as an allowed redirect URI on the OAuth application (or MCP server registration) in your platform. If you operate a SaaS platform with an MCP server and want Barndoor customers to be able to connect to it, add the redirect URI below to your OAuth client allowlist.

Redirect URI to Allowlist

Add this one URI:
  • https://app.barndoor.ai/callback — Production
This URI is stable. It is an exact-match URL — do not add trailing slashes, wildcards, or alternate paths.

Common Platform Locations

Troubleshooting

If users see redirect errors after allowlisting:
  1. Check for exact-match issues. Confirm there are no trailing slashes, missing https://, or typos.
  2. Confirm the change has propagated. Some platforms cache OAuth client config for several minutes.
  3. Contact support if the issue persists: [email protected].

Frequently Asked Questions

No. https://app.barndoor.ai/callback is the only redirect URI customers connect from. Barndoor’s non-production environments are for internal use and are not part of any customer integration.
No. It is a stable, long-lived URI. If it ever changes, Barndoor will notify integrated platforms in advance and update this page.
Most OAuth providers don’t allow wildcards in redirect URIs, and we don’t recommend it even where supported. Register the exact URI above.
No. Redirect URI allowlisting governs the OAuth browser redirect to Barndoor. IP whitelisting governs the server-to-server MCP traffic from Barndoor to your infrastructure. Most integrations need both.

Need Help?

If you have questions about redirect URI allowlisting or need assistance configuring your OAuth application, reach out to our support team at [email protected].