When a user connects to the MontyCloud MCP server with OAuth, you sign in on MontyCloud's page. MontyCloud then sends the result back to the app at its callback URL (also called a redirect URL).
A callback URL belongs to an app, not to a customer. To protect every account, MontyCloud only sends sign-ins to callback URLs on an approved list. This page lists the callback URLs approved today, explains how to request a new one, and has the technical details app developers need.
To connect an app, see MontyCloud MCP Server.
Callback URLs approved today
These apps work without a request:
App | Approved callback URLs |
Claude (claude.ai and Claude Desktop) |
|
ChatGPT |
|
Claude Code |
|
Cursor |
|
Visual Studio Code (GitHub Copilot) |
|
MCP Inspector and the |
|
An approved callback URL works for everyone who uses that app, in each region.
How callback URLs are matched
- Local callbacks (
http://localhost/...andhttp://127.0.0.1/...) match on any port, because desktop and command-line apps pick a free port when they sign in. The path must match exactly. For example,http://localhost:53682/callbackmatcheshttp://localhost/callback, buthttp://localhost:53682/auth/callbackdoesn't. - All other callbacks must match exactly: the same scheme (
https://, or the app's own scheme such ascursor://), host and path. - There are no wildcards. Each callback URL is approved on its own.
When an app's callback URL isn't approved
When you try to connect, the MontyCloud sign-in page shows "This app's callback URL is not allowed" and lists the URLs that aren't approved. Some apps show the problem in their own window instead, as a registration or connection error.
Nothing is wrong with your MontyCloud account. The app only needs its callback URL approved. Until then, you can connect the app with an API key if it supports local MCP servers.
Request a new callback URL
Anyone who uses or develops an app can ask for its callback URL to be approved.
What to send
Email MontyCloud support at support@montycloud.com with:
- The app's name and developer, and a link to the app's MCP or OAuth documentation.
- The exact callback URLs. Copy them from the "This app's callback URL is not allowed" page, or from the app's documentation.
- The kind of app: a web app (HTTPS callback), a desktop app (its own scheme, such as
myapp://), or a local or command-line tool (localhostor127.0.0.1callback). - How the app registers with OAuth servers: Dynamic Client Registration, or a Client ID Metadata Document (include its URL).
- The region where the app is used (US or EU).
- Test access to the app, so MontyCloud can test the sign-in end to end. If the app needs an account, provide a test account, never a personal or production one. Don't put the password in your request; MontyCloud support gives you a secure way to share it.
What MontyCloud checks
- The callback belongs to the app. An HTTPS callback is on the app developer's own domain, and a custom scheme belongs to that app.
- The callback is specific: an exact URL, with no wildcards and no open redirect.
- The app signs in securely, using OAuth 2.1 with PKCE.
- The connection works. MontyCloud connects the app with the test access you provided, signs in, and lists the tools.
Every request is reviewed, and a second MontyCloud reviewer approves it before it goes live.
What happens next
- MontyCloud confirms when the callback URL is approved. You don't need to change anything; connect the app again.
- Approval applies to the app. Once approved, the callback URL works for everyone who uses that app in that region.
- If MontyCloud can't approve the callback URL, support tells you why and what the app developer can change.
- MontyCloud deletes the test access you shared once the review is done.
When an approved callback URL is retired
App developers sometimes change their callback URLs. MontyCloud then retires the old one in two steps:
- Deprecated: apps already connected through it keep working, but a new app can't register with it.
- Disabled: sign-ins through it are refused, and the sign-in page shows "This app's callback URL is not allowed".
If this happens, update the app to its latest version and connect again.
For app developers
The MontyCloud MCP server uses the Streamable HTTP transport and follows the MCP authorization specification. Each region has its own MCP server and authorization server. The authorization server is at https://<api-domain>/oauth2, on the same domain as the MCP server.
Region | Protected resource metadata | Authorization server metadata |
US |
|
|
EU |
|
|
US GovCloud | Not available yet | Not available yet |
The authorization server supports:
- the authorization code flow with PKCE (S256);
- refresh tokens;
- resource indicators, with the
resourceparameter set to the region's MCP server URL; - Dynamic Client Registration;
- Client ID Metadata Documents.
Callback URLs must be on the approved list above. Local callbacks on localhost or 127.0.0.1 can use any port, but the path must match exactly.
Test your connection with MCP Inspector
- Run
npx @modelcontextprotocol/inspector. - Set Transport Type to Streamable HTTP, and enter your region's MCP server URL.
- Choose Connect and complete the sign-in.
- Open Tools > List Tools to see the tools available to your account.
FAQ
Can a callback URL be approved just for my company?
No. Callback URLs are approved per app. Once an app's callback URL is approved, it works for everyone who uses that app.
Does approving a callback URL give the app more access?
No. The callback URL only decides where the sign-in result is sent. The app still acts as the signed-in user, with exactly their MontyCloud permissions, and each user approves each connection on the MontyCloud sign-in page.
My app uses a local callback on a different port each time. Is that a problem?
No. Local callbacks match on any port. Only the path has to match an approved one.