TIP: Connecting Remote MCP Servers to Amazon Quick (stdio proxy method) Tried and tested

Q&A
, , , , , ,
1

Connecting Remote MCP Servers to Amazon Quick (stdio proxy method)

The Problem

Amazon Quick’s built-in MCP OAuth uses RFC 9728 (Protected Resource Metadata discovery). Many third-party MCP servers don’t implement this standard, causing persistent 401 errors — even when the same server works fine in Claude, Cursor, or ChatGPT.

The Solution: mcp-remote as a stdio proxy

Use mcp-remote to wrap any remote MCP server as a local stdio connection. This:

  • Handles OAuth in its own browser window (bypasses Amazon Quick’s discovery)
  • Converts the connection to stdio (the most reliable transport in Amazon Quick)
  • Caches tokens locally after first sign-in

Requirements

  • Node.js 22.16+ (you have v25.9.0 :white_check_mark:)
  • npx (comes with Node.js)

Setup Steps

  1. Settings → Capabilities → MCP Servers → Add
  2. Choose Local/stdio transport
  3. Enter:
    • Command: npx
    • Args: -y mcp-remote@latest <MCP_SERVER_URL>
  4. Save → the server should show as green/connected
  5. On first tool use, a browser window opens for OAuth sign-in → authorise → done

Confirmed Working Servers

Service URL Status
Canva https://mcp.canva.com/mcp :white_check_mark: Connected
Mini Course Generator https://mcp.minicoursegenerator.com/mcp :white_check_mark: Connected

Example Configurations

Canva

  • Command: npx
  • Args: -y mcp-remote@latest https://mcp.canva.com/mcp

Mini Course Generator

  • Command: npx
  • Args: -y mcp-remote@latest https://mcp.minicoursegenerator.com/mcp

Any other remote MCP server

  • Command: npx
  • Args: -y mcp-remote@latest https://<server-url>/mcp

When to Use This Method

Use the stdio proxy when:

  • :cross_mark: Direct SSE connection gives 401 / auth_failed
  • :cross_mark: The MCP server doesn’t serve .well-known/oauth-protected-resource
  • :cross_mark: The OAuth browser popup never appears
  • :cross_mark: The server works in Claude/Cursor but not Amazon Quick

When You Don’t Need This

  • :white_check_mark: The server already works as a direct SSE/HTTP connection in Amazon Quick
  • :white_check_mark: The server uses no authentication
  • :white_check_mark: The server is already local/stdio (e.g., npx packages)

Troubleshooting

  • “npx: command not found” → Node.js not in PATH. Run brew install node@22 or reinstall from nodejs.org
  • Browser window doesn’t open → Check your default browser is set. mcp-remote uses the system default browser (not Amazon Quick’s browser setting)
  • Token expired → Remove and re-add the MCP server in Amazon Quick, or delete the cached token (usually in ~/.mcp-auth/)

Last verified: 17 June 2026 — Amazon Quick v0.1000.1410, macOS arm64

2

Hi @m.abdulqader,
Thank you for sharing this detailed breakdown for the Community!

3

You are most welcome! :grinning_face: