The managed Amazon Agent Atlas endpoint is https://atlas.kuudo.com/mcp, but Kuudo user-account OAuth has not yet been verified. Atlas helps an AI client search Amazon-related knowledge across advertising, Seller Central and Vendor Central topics.
Availability note: Kuudo user-account OAuth for the managed Atlas endpoint is not yet verified. On November 5, 2026, the endpoint required authentication but its OAuth resource-discovery address returned HTTP 401. Check with Kuudo support before relying on the OAuth setup below; an authentication prompt or a live indicator alone does not confirm that connection and tool discovery work.
Endpoints and sign-in
| Purpose | Address |
|---|---|
| MCP server | https://atlas.kuudo.com/mcp |
| OAuth resource discovery, once available | https://atlas.kuudo.com/.well-known/oauth-protected-resource/mcp |
| Intended Kuudo sign-in issuer | https://app.kuudo.com |
The intended user sign-in is OAuth with your Kuudo user account, using the mcp:access permission. After the managed server's OAuth discovery is available, an OAuth-capable client can direct you to Kuudo to sign in, select an organization if prompted, and approve access. The client manages the resulting token.
Atlas is a knowledge server. Its connection does not itself authorize an Amazon Ads, Seller Central, or Vendor Central account. To connect those accounts for live operations, use the corresponding Amazon Ads or Selling Partner guide.
Connect when OAuth is available
- In an MCP client that supports remote HTTP and Kuudo OAuth, add a remote MCP server or custom connector.
- Enter
https://atlas.kuudo.com/mcpas the server URL. - Start the connection. When prompted, sign in with your Kuudo user account, select the intended organization if asked, and approve the requested access.
- Confirm the client lists Atlas tools. Try a question such as: “Find guidance on Amazon listing requirements and show the sources.” Check the returned sources and their applicability to your situation.
Kuudo supports OAuth authorization code with PKCE and client ID metadata documents (CIMD), as well as appropriately preregistered clients. A client that supports only dynamic client registration needs an appropriate Kuudo registration.
Troubleshooting
- The client never opens a Kuudo sign-in page: The managed endpoint may not yet provide OAuth discovery. Contact Kuudo support; do not enter a Google or Amazon credential as a substitute for Kuudo sign-in.
- Sign-in succeeds but tools do not appear: Reconnect and check the client error. Ask support to verify the server and client compatibility; do not share tokens.
- An answer needs verification: Review the cited source and confirm it applies to the relevant account, marketplace, and current Amazon policies.