Axyen (https://www.axyen.ai/home) is a hosted, multi-tenant AI agent and MCP client developed by 23V.
We want Axyen users to connect their Vercel accounts to Vercel’s official MCP server at:
Axyen is not currently on Vercel’s approved MCP-client list, so we are requesting client approval and allowlisting of our OAuth redirect URIs.
Client details:
- Client name: Axyen
- Company: 23V
- Product website: https://www.axyen.ai/home
- Contact: developer.tools@23v.co
- Client type: Hosted multi-tenant MCP client
- Transport: Streamable HTTP
- OAuth: Authorization Code with PKCE S256
- OAuth resource: https://mcp.vercel.com/
- Requested scope: openid
Redirect URIs to allowlist:
Staging: https://api.nmediax.com/api/v1.0/a1/integrations/mcp/remote/callback
Production: https://app.scalaix.com/api/v1.0/a1/integrations/mcp/remote/callback
The nmediax.com and scalaix.com callback domains are part of 23V’s existing backend infrastructure used by Axyen.
Could the Vercel MCP team please:
- Review and approve Axyen as a Vercel MCP client.
- Allowlist both redirect URIs.
- Confirm whether we should use a pre-registered OAuth client, Dynamic Client Registration, or a Client ID Metadata Document.
- Let us know if you require a demonstration, security review, test account, or additional documentation.
Vercel Support directed us to the product/partnerships team and Community for this request. We would appreciate it if an internal ticket could be opened for the MCP team.
Thank you.