Hi Vercel team,
Amiara (https://amiara.ai) is a founder-facing business platform. We are adding Vercel as a connectable partner so a founder can link their own Vercel account and have our AI advisors read their projects, deployments, logs and web analytics through the official Vercel MCP server at https://mcp.vercel.com.
Our client is fully working against mcp.vercel.com in local development, where dynamic client registration accepts a localhost redirect. Registering our production callback is rejected:
POST https://api.vercel.com/login/oauth/register redirect_uris: ["https://api.amiara.com/api/oauth/vercel/callback"] → 400 {"error":"invalid_redirect_uri","error_description":"The provided redirect URIs are not approved for use by this authorization server."}
Could you please allowlist the following redirect URIs for our client?
Details:
- client_name: Amiara
- Client type: hosted, multi-tenant MCP client (public client, PKCE S256, token_endpoint_auth_method "none", authorization_code + refresh_token)
- Scopes: openid offline_access
- Access model: read-only. Our transport enforces an exact-match allowlist of 19 read tools (list/get projects, deployments, logs, analytics, teams). Deploy, purchase and toolbar-write tools are refused before any request reaches Vercel.
- Consent: each founder authorizes their own Vercel account through your consent screen. We store per-organization tokens only.
- Privacy policy: https://amiara.ai/privacy
We are happy to complete any security review and can supply a logo and product description. This is the same request as the kody.codes thread (#48734), which was handled through an internal ticket.
Thank you!