Kuudo Managed MCP lets an MCP-compatible AI client connect to Kuudo-operated services using your Kuudo user account. Choose the server for the work you want to do, add its MCP URL to the client, and follow the Kuudo sign-in and consent flow. For Amazon Ads or Selling Partner operations, the relevant Amazon account also needs a separate authorization in your organization.
Choose a managed server
| Managed server | What it helps with | MCP URL | Setup |
|---|---|---|---|
| Amazon Ads | Advertising accounts, campaigns and reporting | https://ads.kuudo.com/mcp | Ads setup |
| Amazon Selling Partner | Seller Central and Vendor Central operations | https://sp.kuudo.com/mcp | Selling Partner setup |
| Amazon Agent Atlas | Amazon operating knowledge and source material | https://atlas.kuudo.com/mcp | Atlas setup |
| Amazon Agent Iris | Image and video creation and review | https://iris.kuudo.com/mcp | Iris setup |
Seller and vendor accounts use the Selling Partner endpoint; select the appropriate account type and authorization. The Vendor Central setup explains the vendor path. Client compatibility and tool availability can vary, so check that the client connects and lists the tools needed for your task.
Atlas availability: As of November 5, 2026, Atlas's OAuth resource-discovery endpoint returns HTTP 401 and its Kuudo user sign-in flow has not been verified. Check with Kuudo support before relying on that flow. For Iris, OAuth discovery is available, but the deployed Google credential header and an authenticated generation request have not yet been verified. See the individual guides for details.
Authorize the Amazon account separately
A Kuudo sign-in connects your client to the managed service; it does not by itself authorize an Amazon account. For Ads or Selling Partner, connect the Amazon account in the intended Kuudo organization, or invite an account owner to grant access. Ads and Selling Partner require separate authorizations. Confirm the selected account and marketplace or advertising profile before making a request.
Atlas supplies knowledge rather than live Amazon account data. Iris has a separate provider credential for Google-backed generation; Amazon account consent does not configure it.
Connect an OAuth-capable client
- Add a remote MCP server or custom connector in your client and enter the chosen MCP URL from the table.
- Start the connection. When prompted, sign in with your Kuudo user account, select the intended organization if asked, and review the requested permissions.
- Confirm the client shows the server as connected and lists its tools. For Ads or Selling Partner, choose an authorized account and run a read-only request before making changes.
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. Client setup and compatibility vary; a successful browser sign-in alone does not prove that tool discovery works.
OAuth discovery addresses
OAuth-capable clients normally discover these shared Kuudo addresses automatically. Enter the individual MCP URL above when adding a server; these addresses do not replace it.
| Purpose | Address |
|---|---|
| Issuer | https://app.kuudo.com |
| Authorization server metadata | https://app.kuudo.com/.well-known/oauth-authorization-server |
| Authorization | https://app.kuudo.com/api/auth/oauth2/authorize |
| Token exchange | https://app.kuudo.com/api/auth/oauth2/token |
The client manages the OAuth token. Keep any credentials or provider keys in your client's secure connection settings rather than sharing them in a chat or support request.
Next steps
Follow the service guide for prerequisites, a first request and troubleshooting. If the client signs in but cannot list tools, reconnect and contact Kuudo support with the client name and time of the attempt; do not share tokens.
For the other deployment option, see Choose Managed MCP or Private Cloud.