Skip to content

Compare Amazon MCP servers

agentcentral (Agent Central) vs Kuudo for Amazon MCP

agentcentral, called Agent Central on its homepage, is a hosted Amazon MCP server: connect by OAuth and it syncs your Seller Central and Ads data to its cloud, which is what makes reads fast. Kuudo provisions the servers into your own cloud account, on your own Amazon app, and ships Skills above the tools.

Kuudo facts come from the Kuudo MCP servers reference and the cloud deployment guides. agentcentral facts come from their own docs, pricing, and llms.txt, with the date each one was checked.

Thomas Spicer Updated

Whose infrastructure each piece sits on
  1. Where the server runs: agentcentral, Their cloud; Kuudo, Your cloud.
  2. Where Amazon calls route: agentcentral, Through their cloud; Kuudo, Direct to Amazon.
  3. Where your Amazon data sits: agentcentral, Their cloud; Kuudo, Your cloud.
  4. Where a read comes from: agentcentral, Their sync; Kuudo, Amazon.

agentcentral does 0 of the 4 steps; Kuudo does 4 of the 4.

Compared on · agentcentral facts checked

At a glance

agentcentral vs Kuudo, the short version.

All 20 rows, one line per cell. The sourced sentence behind each line, with the page it was checked against and the date, is in the full table below.

agentcentral (Agent Central) vs Kuudo for Amazon MCP: 20 criteria at a glance
CriterionagentcentralKuudo
The Amazon MCP connection, from connecting the account through to a change going live
Where it runsTheir cloud only, one hosted endpoint1Your own cloud account17
Your Amazon credentialsThey store and refresh your tokens2Kuudo encrypts the token; app can be yours18
Where calls routeYes, through their infrastructure3Direct to Amazon, per the DPA18
Where your data sitsOn their infrastructure, U.S. Google Cloud2Lake in your own cloud21
Live or syncedTheir sync; a subset of tools live310A read calls Amazon22
Tool surface175 or 144 tools, by page451,055 Amazon API operations22
WritesYes, 80 write tools by their count710Yes, on all three servers22
What guards a writePreview unless the calling agent confirms7Workspace policy; approval may be required22
What is recordedWrites logged with old and new values3Every tool call, in a run log22
Above the toolsNone ship, by design; build your own820 Skills (2 Kuudo-certified); write your own23
Beyond an MCP endpoint
Amazon Ads101 tools: sponsored ads, DSP reads7711 Amazon Ads operations24
Amazon Marketing CloudBid adjustments on AMC audiences7Amazon Marketing Cloud queries and audiences22
Seller operationsInventory, orders, catalog, finance, fulfillment9304 Selling Partner operations25
Vendor CentralNot offered, in their own words1040 Vendor Central operations22
CreativeNot offered, by their stated scope7Agent Iris images and product video6
Operating knowledgeNone by design; facts only10Agent Atlas operating playbooks and rules26
Where you use itClaude, ChatGPT, Grok Bot, any MCP client1116Claude, ChatGPT, or any MCP client19
How it runs, and how you buy it
Pricing model$39 to $159 or $199, by page1213105Community free; paid plans per API call20
Seats and organizationsSeat limit not published131425 seats on Pro, 50 on Scale19
Free tier14 days, no credit card1315Community free, no time limit19

Side by side

Where agentcentral and Kuudo actually differ.

20 rows. The first 10 follow the Amazon MCP connection step by step, from connecting the account through to a change going live: what agentcentral does at each step and how Kuudo does it. Beyond an MCP endpoint, you get your Amazon Ads, Amazon Marketing Cloud, seller operations, Vendor Central, image and video generation, Amazon operating knowledge, and the AI clients you want to use. Each competitor cell links to the page it was checked against and the date.

agentcentral (Agent Central) vs Kuudo for Amazon MCP: 20 criteria compared side by side
CriterionagentcentralKuudo
The Amazon MCP connection, from connecting the account through to a change going live
Where it runs Whose cloud runs the server?Their cloud only, through one shared hosted endpoint. Their public GitHub repository holds registry metadata and a stdio introspection stub rather than the server, and states that live tool execution happens only through the hosted endpoint.1Your own AWS, Google Cloud, Azure, or Cloudflare account. Kuudo provisions a private MCP server environment into the cloud account you pick, and you own the deployment, the data, and the perimeter.17
Your Amazon credentials Who holds the tokens to my Amazon account?They do. You authorize Amazon Ads and Seller Central by OAuth in their dashboard, and agentcentral stores and refreshes those tokens encrypted at rest. It does not expose raw Amazon tokens to the agent.2Kuudo's authorization service receives and encrypts an Amazon refresh token, and in bring-your-own-app mode your application secret, then exchanges them for short-lived access tokens it issues to runtimes you authorize. The Amazon app can be your own, and the substantive API traffic does not route through Kuudo.18
Where calls route Do my Amazon requests route through the vendor?Yes, by architecture. Reads are served from data they have already synced into their own storage, and the tools they mark live call Amazon from their infrastructure, so the request path runs through them.3No. The DPA commits that your cloud resources connect directly to Amazon's business-data APIs, and that substantive API requests and responses do not proxy, relay, or route through Kuudo infrastructure.18
Where your data sits Where does my Amazon data end up?On their infrastructure. Amazon data is synced ahead of time into account-isolated storage on Google Cloud Platform in the United States, kept while the account is active, and not used to train models. Their comparison page puts the standard history at 30 days with eligible backfills to one year, and a read-only JSON API is the published way out.2In your cloud. Agent Flow lands Amazon data in a lake in your own account, and Snowflake, Athena, DuckDB, Databricks, Power BI, and Tableau can read it downstream.21
Live or synced When my agent reads, is it calling Amazon or a copy?From their sync, by design. Ads data refreshes daily and business reports roughly every 72 hours. Their pages disagree on read speed: most reads return in under 300 milliseconds on the platform guide, and prepared-data reads in under a second on their DataDoe comparison page. A subset of tools are marked live and call Amazon directly.310From Amazon. The tools are Amazon's own API operations exposed over MCP, so a read is a call to Amazon. Agent Flow adds scheduled refreshes and lake tables in your own cloud when you want stored history.22
Tool surface What can my agent reach, and how is it counted?Their pages disagree on the count: 175 tools across six data domains on the tool reference, and 144 domain-scoped tools, 148 in total, in their llms.txt. These are tools rather than underlying Amazon API operations, so neither number is comparable to an operation count.451,055 Amazon API operations exposed as tools across three servers: 711 Amazon Ads, 304 Selling Partner, and 40 Vendor Central.22
Writes Can it change my Amazon account?Yes, extensively. Their comparison page puts the total at 80 guarded write tools, and the Ads reference splits its 101 tools into 30 read, 60 write, and 11 live, covering campaigns, ad groups, ads, keywords, targets, bids, budgets, and states, plus prices, inventory quantities, listings, and order fulfillment.710Yes. Every tool on every server is tagged read or write, and write tools exist across all three servers.22
What guards a write What stands between the agent and a change?A write returns a preview unless the caller sets confirm to true and supplies an idempotency key, with hard limits, a pre-read, and an audit entry holding the previous and new values. API keys can be issued read-only or scoped to one domain, which the server enforces. The confirmation is a parameter the calling agent supplies.7Write tools are guarded: they validate input, apply your workspace policy, and may require explicit human approval before a change reaches Amazon.22
What is recorded What can I review afterward?Write actions are logged with their old and new values, and the ads tools read current values first to build that trail. A log of the reads an agent performed is not described.3Every tool call records the requesting user, agent, workspace, parameters, result summary, and approval state, across every server, in a run log you can use to reproduce an output or review a change.22
Above the tools What comes with it besides tool access?None ship with the product, deliberately. Their best-practice documentation teaches you to build your own prompt library by iterating in conversation and to hand-author a business playbook in Markdown that the agent loads.820 Skills (2 Kuudo-certified) ship with the platform, each stating the job it does, the inputs it needs, the outputs it returns, and the limits it keeps, and you can write your own in the same format.23
Beyond an MCP endpoint
Amazon Ads Can it run my Amazon Ads?Advertising is their largest domain, with 101 tools covering campaigns, ad groups, ads, keywords, and targets across Sponsored Products, Brands, and Display. Three of them read Amazon DSP: order, line item, and creative performance, and live DSP advertisers, campaigns, ad groups, and targets.7711 Amazon Ads operations across Sponsored Products, Brands, Display, and TV, plus DSP, the unified Ads API v1, attribution, and reporting, through the Amazon Ads MCP.24
Amazon Marketing Cloud Can it query Amazon Marketing Cloud?Their Ads reference mentions it twice, in their words: the targeting-options tool says "AMC is out of scope", and the campaign audience bid adjustment tool takes SPONSORED_ADS_AMC for AMC custom audiences. No tool on that reference runs Amazon Marketing Cloud queries.7Yes. Amazon Marketing Cloud queries and audiences run through the Amazon Ads MCP.22
Seller operations Can it run orders, inventory, pricing, and catalog work?Yes. Selling Partner coverage spans inventory and orders, catalog, finance, and fulfillment, and they state all 23 Amazon marketplaces are enabled and self-serve.9304 Selling Partner operations for catalog, listings, orders, pricing, FBA, fulfillment, and finances, through the Amazon Selling Partner MCP.25
Vendor Central Can it run Vendor Central work?Not offered. They say so on their own comparison page and treat it as a point in a competitor's favour when Vendor Central is a hard requirement.1040 Vendor Central operations: purchase orders and acknowledgements, direct fulfillment, shipments and invoices, transaction status, Retail Analytics, Data Kiosk, and A+ Content.22
Creative Can it generate listing and ad creative, images and video?Their Ads tool reference states that agentcentral does not generate or recommend ad creative, and that the caller must provide the documented creative object when creating a Sponsored Brands ad. Their catalog tools read and update listing content, including image URLs, without producing the images themselves. That is a scope choice rather than a gap: their published boundary is a facts layer that returns source-provided fields, deterministic metrics, and audited write results.7Yes. Agent Iris generates and audits listing images, and creates, edits, or extends owned product videos with Google Gemini Omni. Approved images publish through the Selling Partner MCP with ingestion checks; video assembly and final upload remain external.6
Operating knowledge Does it bring Amazon know-how to the job?By design, none. They state the product returns facts, source fields, deterministic metrics, and classifications, and does not author recommendations or next actions, because deciding what to do is your agent's job.10Agent Atlas supplies curated Amazon operating playbooks and rules that your agent retrieves before it acts.26
Where you use it Which apps can I use it from?A remote MCP server, plus a local stdio bridge through their command-line tool for clients that only support local servers. Their homepage names Claude, Claude Code, ChatGPT, Grok Bot, OpenClaw, and Hermes Agent, and any AI client that supports MCP.1116Claude, ChatGPT, Cursor, Copilot, n8n, or any MCP client.19
How it runs, and how you buy it
Pricing model How is it priced?Five tiers metered on distinct monthly Amazon order IDs: $39 a month to 1,000 orders, $69 to 5,000, $99 to 10,000, a Business tier to 20,000, and custom above that. Their pages disagree on Business: $159 a month on their pricing docs and their DataDoe comparison page, which says "$39 to $159/month", and $199 in their pricing.md and llms.txt. Extra ads or brand profiles on the same marketplace are $19 a month each.1213105Kuudo Community is free for one instance of each Amazon MCP server in your own cloud. Kuudo Pro is $0 a month plus $0.95 per 1,000 Amazon API calls, and Kuudo Scale is $249 a month plus $0.55 per 1,000 Amazon API calls. The calculator models a month for a brand owner, an agency or aggregator, and an automation-heavy seller.20
Seats and organizations How many people and accounts?No seat or user limit is published. One subscription covers an Amazon seller account with its marketplaces included, and access is granted per API key, with each key scoped to one marketplace.1314Kuudo Pro: up to 25 seats across 5 organizations. Kuudo Scale: up to 50 seats across 10 organizations. Enterprise: unlimited.19
Free tier Can I try it free?14 days with no credit card and the full tool surface, after which billing starts at their entry tier and adjusts to actual order volume. A public demo account with sample data and simulated writes connects through a shared public connector URL.1315Kuudo Community includes 10,000 free Amazon API calls per month, with one instance of each Amazon MCP server in your own cloud.19

Their fit

Choose agentcentral if

Real situations where agentcentral is the better buy. If one of them is yours, buy it.

  • You want pricing based on the number of orders.

    agentcentral meters its plans on distinct monthly Amazon order IDs. Your order volume determines your pricing tier.

  • You want a limited set of preset options that fit your use case.

    Their defined tool set covers specific Seller Central and Ads tasks. Those options already match the work you want your agent to do.

  • Amazon AUP and DPP compliance is less central to your buying decision.

    You are comfortable choosing a hosted service that stores your Amazon data and routes requests through its infrastructure, with less emphasis on evaluating that setup against Amazon's Acceptable Use Policy and Data Protection Policy.

Our fit

Choose Kuudo if

Where Kuudo is the better buy: the servers and the data sit in infrastructure you own, the Amazon app can be yours, and Skills sit above the tools. Beyond an MCP endpoint, you get your Amazon Ads, Amazon Marketing Cloud, seller operations, Vendor Central, image and video generation, Amazon operating knowledge, and the AI clients you want to use.

  • The whole Amazon job

    You need Vendor Central or Amazon Marketing Cloud, not just seller and ads.

    Vendor Central runs through its own MCP server, Amazon Marketing Cloud queries and audiences run through the Amazon Ads MCP, and Agent Iris generates listing images and product video from the same agent: 711 Amazon Ads, 304 Selling Partner and 40 Vendor Central operations, with the operating context from Agent Atlas.

  • Your AI client

    Your AI client is already chosen, and the server should meet it there.

    Kuudo connects to Claude, Claude Desktop, Claude Cowork, Claude Code, ChatGPT, Codex, Cursor, n8n and any other client that speaks Model Context Protocol, on your own Amazon app rather than a shared one.

  • Your rules

    You want playbooks that state their own limits, and the format to write your own.

    20 Skills (2 Kuudo-certified) ship with the platform, each stating the job, the inputs, the outputs, and what it is not for, and you can write your own in the same format.

  • Ownership

    The deployment should be an asset you own, not an endpoint you rent.

    Kuudo provisions private MCP server environments into your own AWS, Google Cloud, Azure, or Cloudflare account, and you own the deployment, the data, and the perimeter. The DPA commits that your cloud resources connect directly to Amazon and that substantive requests and responses do not route through Kuudo, and Agent Flow lands stored data in a lake in your own account. Private. Trusted. Owned.

  • Control

    You need a record of what an agent did, and a gate you control before it does it.

    Write tools apply your workspace policy and may require explicit human approval, and every call is recorded with its parameters and approval state in a run log.

The differences that matter

5 questions that decide agentcentral vs Kuudo.

Each one opens with the answer, then what each product does, then what it means for the person doing the work.

Whose cloud runs the server?

agentcentral runs one hosted endpoint on its own infrastructure. Kuudo provisions private MCP server environments into the cloud account you choose.

agentcentral

One shared hosted endpoint. Their public repository holds registry metadata and a stdio introspection stub, and says live tool execution happens only through the hosted endpoint, so there is no self-host path.

Kuudo

Kuudo provisions the servers into your own AWS, Google Cloud, Azure, or Cloudflare account, from the app, with a per-provider activation guide. You own the deployment, the data, and the perimeter.

What it means for you. Hosted is faster to start and someone else runs it. Owned means the environment, the credentials, and the data stay inside a perimeter you control, and switching AI clients does not mean moving your Amazon connection.

Cloud deployment destinations

Where does my Amazon data end up?

agentcentral syncs your Amazon data into its own storage and serves reads from there. Kuudo reads through Amazon's API and, when you want stored history, lands it in a lake in your cloud.

agentcentral

Synced ahead of time into account-isolated storage on Google Cloud Platform in the United States, kept while the account is active, and not used to train models. A read-only JSON API is the published way to get data out.

Kuudo

Agent Flow lands Amazon data in a lake in your own cloud account using durable ingestion, Iceberg tables, and scheduled refreshes, and Snowflake, Athena, DuckDB, Databricks, Power BI, and Tableau read it downstream.

What it means for you. One model puts a copy of your Amazon data on a vendor's infrastructure and answers fast from it. The other keeps the copy, if you want one, in the account you already own and audit.

Amazon Agent Flow documentation

What comes with it besides tool access?

agentcentral ships tools and, deliberately, no opinions. Kuudo ships Skills that state their own limits, plus operating knowledge your agent retrieves before it acts.

agentcentral

No packaged playbooks, skills, or workflows. Their best-practice docs teach you to build a prompt library by iterating in conversation and to hand-author a business playbook in Markdown that the agent loads at the start of a session.

Kuudo

20 Skills (2 Kuudo-certified) ship with the platform, each publishing the job it does, its inputs and outputs, and what it is not for, and Agent Atlas supplies curated Amazon operating playbooks and rules that your agent retrieves before it acts. You can write your own Skills in the same format.

What it means for you. Raw tools plus your own prompts is the most flexible starting point and the slowest one. Shipped playbooks that state where they stop are faster, and the published limits are what make them safe to run unattended.

Amazon Agent Skills reference

Do my Amazon requests route through the vendor?

agentcentral serves reads from a copy it holds and calls Amazon from its own infrastructure. Kuudo commits contractually that substantive Amazon traffic never routes through it.

agentcentral

Yes, by architecture. Reads come from data synced into their storage ahead of time, and the tools they mark live call Amazon from their infrastructure, so both the request and the response pass through them.

Kuudo

The DPA commits that your cloud resources connect directly to Amazon's business-data APIs, that substantive API requests and responses do not proxy, relay, or route through Kuudo, and that client tools connect directly to your resources rather than through Kuudo. Kuudo's authorization service is the documented exception, and it handles tokens rather than your Amazon data.

What it means for you. This is the row that decides what a breach at the vendor could reach. With one, your Amazon reads and writes are on their wire. With the other, the commitment is that they are not, and the exception is written down.

Customer-controlled architecture

What stands between the agent and a change?

Both guard writes, by different mechanisms. agentcentral previews unless the agent confirms, and scopes keys. Kuudo applies your workspace policy and may require a person.

agentcentral

A write returns a preview unless the caller sets confirm to true with an idempotency key, and keys can be issued read-only or scoped to a single domain, which the server enforces regardless of local flags. The confirmation is a parameter the calling agent supplies, not a separate sign-off.

Kuudo

Write tools validate input, apply your workspace policy, and may require explicit human approval before a change reaches Amazon, and every call is recorded with its parameters and approval state in a run log you can replay.

What it means for you. Key scoping is the stronger of their two controls, because a read-only key cannot be talked into a write. A policy gate answers a different question: who signs off when the agent is allowed to write and is about to.

Read and write tools

Running both

Run both from one client.

MCP clients connect to many servers at once, so nothing stops you from having both. The split that makes sense is coverage: theirs for the fast synced reads it is built for, Kuudo for Vendor Central, Amazon Marketing Cloud, and anything that writes under your own approval policy.

  1. Step 1

    Add both servers to your MCP client; clients hold several connections at once.

  2. Step 2

    Let their tools answer the Seller Central and Ads reads they have already synced.

  3. Step 3

    Send Vendor Central and Amazon Marketing Cloud work to Kuudo, which covers both.

  4. Step 4

    Route anything that writes through Kuudo, so one approval policy and one run log cover every change.

Methodology

How we compared

Every fact on this page links to the page that states it, with the date it was checked. What we could not verify is listed, not guessed.

Competitor facts come from pages the competitor publishes. Kuudo facts come from Amazon Agent Iris documentation, Cloud deployment destinations, Kuudo data processing addendum, Kuudo pricing, Kuudo pricing calculator, Amazon Agent Flow documentation, Kuudo MCP servers reference, Amazon Agent Skills reference, Amazon Ads MCP tools reference, Amazon Selling Partner MCP tools reference, Amazon Agent Atlas documentation. Planned work is cited to the roadmap and worded as planned. This page compares tools. For the job itself, see what your AI does once it is connected; for Kuudo's side of it, see Kuudo MCP and the Amazon Selling Partner MCP.

Sources

  1. 1 agentcentral public GitHub repo checked
  2. 2 agentcentral privacy policy checked
  3. 3 agentcentral docs: platform guide checked
  4. 4 agentcentral tool reference checked
  5. 5 agentcentral llms.txt checked
  6. 6 Amazon Agent Iris documentation checked
  7. 7 agentcentral Ads tool reference checked
  8. 8 agentcentral docs: business playbook checked
  9. 9 agentcentral Amazon Seller Central MCP page checked
  10. 10 agentcentral: vs DataDoe checked
  11. 11 agentcentral homepage checked
  12. 12 agentcentral pricing.md checked
  13. 13 agentcentral docs: pricing checked
  14. 14 agentcentral docs: scope your API keys checked
  15. 15 agentcentral public demo checked
  16. 16 agentcentral docs: local MCP bridge checked
  17. 17 Cloud deployment destinations checked
  18. 18 Kuudo data processing addendum checked
  19. 19 Kuudo pricing checked
  20. 20 Kuudo pricing calculator checked
  21. 21 Amazon Agent Flow documentation checked
  22. 22 Kuudo MCP servers reference checked
  23. 23 Amazon Agent Skills reference checked
  24. 24 Amazon Ads MCP tools reference checked
  25. 25 Amazon Selling Partner MCP tools reference checked
  26. 26 Amazon Agent Atlas documentation checked

What we could not verify

  • An earlier read found agentcentral's homepage saying five data domains; on 2026-09-26 the homepage gives no count, and the tool reference says six while publishing tool counts for five.
  • Whether agentcentral offers an approval step outside the calling agent: confirm is a parameter the agent supplies, and no dashboard queue or second-party sign-off is described.
  • Whether agentcentral records the reads an agent performed; only write logging is documented.
  • Whether agentcentral can export in bulk to a customer's warehouse; a read-only JSON API is the only programmatic way out that is published.
  • agentcentral's team size, funding, named customers, uptime commitment, and security certifications: none are published, and their terms say they aim for high availability without committing to it.
  • A like-for-like surface comparison: agentcentral publishes tool counts and Kuudo publishes Amazon API operation counts, which are not the same unit.

If you work at agentcentral and something here is wrong or out of date, tell us and we will fix it. Contact us.

Frequently asked questions

Questions sellers ask before choosing between agentcentral and Kuudo.

Hosting, credentials, coverage, what ships above the tools, and whether you need both.

Is agentcentral better than Kuudo?
For fast reads over data they have already synced, and for pricing metered on order volume, agentcentral is the better fit. For owning the deployment, keeping your Amazon traffic off a vendor's wire, reaching Vendor Central and Amazon Marketing Cloud, and starting from playbooks that state their own limits, Kuudo is. The rows on this page are the way to decide, and every cell links to the page it came from.
Can I use agentcentral and Kuudo together?
Yes. MCP clients connect to several servers at once, so both can be available in the same session. The split that makes sense is coverage: theirs for the synced Seller Central and Ads reads it is built for, Kuudo for Vendor Central, Amazon Marketing Cloud, and anything that writes under your own approval policy.
Where does each one store my Amazon data?
agentcentral syncs your Amazon data ahead of time into account-isolated storage on Google Cloud Platform in the United States, keeps it while the account is active, and states it is not used to train models. Kuudo provisions the MCP servers into your own AWS, Google Cloud, Azure, or Cloudflare account, and Agent Flow lands data in a lake there, so the copy stays in an account you already own. Tokens are the documented exception on both sides: Kuudo's authorization service receives and encrypts an Amazon refresh token, and your application secret in bring-your-own-app mode, but the DPA commits that substantive Amazon requests and responses do not route through Kuudo.
Does agentcentral cover Vendor Central or Amazon Marketing Cloud?
Vendor Central, no. They state that plainly on their own comparison page and call it a point in a competitor's favour when Vendor Central is a hard requirement. Amazon Marketing Cloud appears twice on their Ads reference: one tool says "AMC is out of scope", and the campaign audience bid adjustment tool takes AMC custom audiences. No tool there runs AMC queries. Kuudo runs Vendor Central through its own MCP server and Amazon Marketing Cloud through the Amazon Ads MCP.
Which one writes to my Amazon account, and what guards it?
Both write, by different mechanisms. agentcentral returns a preview unless the calling agent sets confirm to true with an idempotency key, and API keys can be issued read-only or scoped to one domain, which their server enforces. On Kuudo, write tools validate input, apply your workspace policy, and may require explicit human approval, and every call is recorded with its approval state in a run log.
What does each one cost?
agentcentral publishes five tiers metered on distinct monthly Amazon order IDs, from $39 a month up to 1,000 orders to a Business tier up to 20,000, which their pricing docs and DataDoe comparison page put at $159 a month and their pricing.md and llms.txt at $199, with extra ads or brand profiles at $19 a month each, and a 14-day trial with no card. Kuudo Community is free for one instance of each MCP server in your own cloud; Kuudo Pro is $0 a month plus $0.95 per 1,000 Amazon API calls, and Scale is $249 plus $0.55 per 1,000.
Can I self-host agentcentral?
No. Their public GitHub repository holds registry metadata and a stdio introspection stub rather than the server itself, and states that live tool execution happens only through the hosted endpoint. Kuudo is the opposite shape: it provisions private MCP server environments into a cloud account you pick, with per-provider activation guides for AWS, Google Cloud, Azure, and Cloudflare.

The bottom line

Own the deployment your agent works through.

Kuudo provisions the Amazon Ads, Selling Partner, and Vendor Central MCP servers into your own cloud account, on your own Amazon app, with Skills above the tools. Community is free.