idealo MCP auth proxy
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@idealo MCP auth proxycompare prices for iPhone 15 Pro"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
idealo MCP auth proxy
A small local stdio bridge so Cursor can use the official idealo MCP server while Idealo's OAuth allowlist does not yet include Cursor's current redirect URI.
The same pattern applies to any remote MCP that uses OAuth + Dynamic Client Registration against a strict identity provider (AWS Cognito, Okta, Auth0, …) that only allowlists a subset of client callbacks.
Why this proxy exists
Cursor can talk to remote MCP servers over HTTP and run the OAuth handshake itself. That used to work with idealo.
Cursor then changed the desktop MCP callback from a custom scheme to an RFC 8252 loopback URL:
Surface | Redirect URI |
Older Cursor desktop |
|
Current Cursor desktop |
|
Cursor web / agents |
|
See the Cursor MCP docs (http://localhost:8787/callback for desktop). There is no mcp.json field to pick a different redirect URI.
idealo fronts Cognito and exposes Dynamic Client Registration at https://mcp.idealo.com/oauth2/register. Registration does not create a new Cognito app per client. Every successful registration is mapped onto one shared Cognito client. Only redirect URIs on that client's allowlist work. As of September 2026 that list includes Claude Code and the old Cursor custom scheme, but not the current Cursor loopback URL:
Redirect URI | Idealo DCR / Cognito |
| allowed |
| allowed |
| allowed |
| allowed |
| rejected ( |
| rejected |
So Cursor opens Cognito with redirect_uri=http://localhost:8787/callback, Cognito answers redirect_mismatch, and the browser shows “Something went wrong”. Mapping cursor:// to port 8787 does not help: Cursor never sends that URI anymore, so Cognito never redirects to it.
This repo does not try to change Cursor's redirect. It takes Cursor out of the OAuth path:
Cursor starts a local stdio process (no remote OAuth, no
:8787).That process is
mcp-remote.mcp-remoteregisters and authorizes with the callback idealo already allowlists:http://localhost:6274/callback.After login, it forwards MCP calls to
https://mcp.idealo.com/mcpwith the bearer token.
Once idealo allowlists Cursor's current callbacks, you can delete this proxy and put the remote URL back in mcp.json.
Related MCP server: Google Docs MCP Proxy
Setup
git clone <this-repo> idealo-proxy
cd idealo-proxy
npm installIn ~/.cursor/mcp.json, replace a remote url entry with a command that runs the wrapper (use your clone path):
{
"mcpServers": {
"idealo": {
"command": "node",
"args": [
"/absolute/path/to/idealo-proxy/bin/idealo-mcp.js"
]
}
}
}Reload the idealo MCP server in Cursor. On first connect a browser window opens for idealo login. Tokens are cached under ~/.mcp-auth.
License
Copyright (c) 2026 Sebastian Schmittner
This project is released under the MIT License (OSI-approved). The full text is in LICENSE:
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted OAuth MCP at https://www.taskade.com/mcp, or local @taskade/mcp-server.
Connect AI agents to Filepad workspaces through OAuth MCP.
StremAI MCP: shared memory for AI coding agents. Connected agents can recall. OAuth + local stdio.
Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceBridges stdio-based LLM harnesses to OAuth-protected remote MCP servers via Streamable HTTP, handling PKCE browser login and token refresh automatically.4 npm-
- AlicenseNot gradedqualityDmaintenanceLocal stdio MCP server that handles Google OAuth2 locally and proxies authenticated requests to Google Docs and Google Drive REST APIs, enabling document and file operations from Cursor or other MCP clients.46 npmMIT
- AlicenseNot gradedqualityAmaintenanceBridge that lets stdio-only MCP clients connect to remote MCP servers with OAuth and other auth support, enabling local clients to use remote, authorized MCP servers.60 npm54MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to connect to remote servers that have OAuth issuer mismatches (e.g., OutSystems) by relaying stdio and handling OAuth flows with optional issuer override.6 npmMIT