Skip to main content

Troubleshooting MCP Connections

How to resolve common MCP connection issues, including where to find the elvex OAuth callback URL for third-party OAuth app registration.

When setting up a custom MCP (Model Context Protocol) server in elvex, you may run into OAuth configuration errors β€” especially when the third-party service asks you to register a redirect or callback URL.

Finding the elvex OAuth Callback URL

When you connect an MCP server that uses OAuth (such as Google Ad Manager, Canva, or Airtable), the third-party service will ask you to register a redirect URI or callback URL in their OAuth app settings. This is the URL the service sends users back to after they authorize access.

You might need this when:

  • Setting up a custom MCP integration that requires you to register your app in the provider's developer console

  • Connecting an OAuth-based MCP and seeing an error like "redirect URI mismatch" or "invalid callback URL"

  • A provider's setup guide asks you to whitelist a redirect URL before OAuth will work

The elvex callback URL

Use the following URL wherever the third-party service asks for a redirect URI, callback URL, or OAuth return URL:

Steps

  1. Open the third-party service's developer or OAuth settings (e.g., Google Cloud Console, Canva Developer Portal, Airtable OAuth app settings).

  2. Find the field labeled Redirect URI, Callback URL, or Authorized redirect URIs.

  3. Return to elvex and complete the MCP connection setup.

Note: Some services allow multiple redirect URIs β€” make sure you add elvex's URL without removing any existing ones.

Still having trouble?

If you've completed the steps above and your MCP connection still isn't working, reach out to elvex support. When you do, include:

  • The name of the MCP server you're trying to connect

  • The error message you're seeing

  • A screenshot of your OAuth app settings (with any client secrets redacted)

This helps the support team diagnose the issue faster.

Did this answer your question?