Skip to content
Talk to Us

Blocks.ai publishes this comparison and sells in this market. Every claim about another product links to a public source.

Amazon Bedrock AgentCore vs Cloudflare MCP server portals

Amazon Bedrock AgentCore

AWS platform for building, deploying, and operating AI agents

Cloudflare MCP server portals

Cloudflare One feature that puts MCP servers behind one governed endpoint

Short answer

Amazon Bedrock AgentCore is AWS’s platform for building, deploying, and operating agents, while Cloudflare says its MCP server portals, a feature of Cloudflare One, put MCP servers behind one governed endpoint.⁠Source 1, Source 2, Source 3, Source 4 AgentCore can host agents and catalogs agents as well as tools; a portal lists MCP servers and applies Cloudflare Access policies to whoever connects.⁠Source 1, Source 3, Source 5

By Blocks.ai teamLast checked

Where each one sits

Six layers of running AI agents at a company, and what each product’s own public sources say it covers.

These aren’t the same kind of product

Where they overlap
Both put MCP servers behind one authenticated endpoint: an AgentCore Gateway acts as one MCP server combining its MCP targets, and a portal centralizes MCP servers on one HTTP endpoint.⁠Source 3, Source 6, Source 7
Where they differ
AgentCore also hosts agents in its Runtime and catalogs agents, not only tools.⁠Source 1, Source 5 Portals list MCP servers; a registry of agents is not publicly documented.⁠Source 3
Running both
Each works with MCP servers it doesn’t run: AWS Agent Registry works with MCP servers on premises or in other clouds, and portal admins can manage third-party MCP servers.⁠Source 1, Source 4
Public sources · checked 2 October 2026
  • Offered
  • Not publicly documented

Amazon Bedrock AgentCore

  • Build agents: OfferedHarness managed agent loop⁠Source 1
  • Host and run agents: OfferedAgentCore Runtime⁠Source 1
  • Identity and access: OfferedAgentCore Identity workload identities⁠Source 8
  • Registry and governance: OfferedAWS Agent Registry with approvals⁠Source 5
  • Traffic between agents, tools, and models: OfferedAgentCore Gateway⁠Source 9
  • Agents across organizations: OfferedRegistry shared through AWS RAM⁠Source 10

Cloudflare MCP server portals

  • Build agents: Not publicly documented
  • Host and run agents: Not publicly documented
  • Identity and access: OfferedIdentity provider or service token⁠Source 3
  • Registry and governance: OfferedCentrally managed MCP servers⁠Source 3
  • Traffic between agents, tools, and models: OfferedProxy for MCP tool calls⁠Source 3
  • Agents across organizations: Not publicly documented

At a glance

TopicAmazon Bedrock AgentCoreCloudflare MCP server portals
What it isAWS’s platform for building, deploying, and operating agents, made of modular services you can use together or independently.⁠Source 1Puts multiple MCP servers behind one HTTP endpoint, governed through Cloudflare Access.⁠Source 3, Source 4 Cloudflare says portals are a feature of Cloudflare One, its SASE platform.⁠Source 2
What it catalogsAgents, MCP servers, tools, agent skills, and custom resources, in AWS Agent Registry behind an approval workflow.⁠Source 5MCP servers and their tools, up to 80 servers per portal.⁠Source 3 A registry of agents is not publicly documented.
How agents are identifiedWorkload identities in AgentCore Identity, for agents on AgentCore Runtime, self-hosted, or in hybrid deployments.⁠Source 8, Source 11As MCP clients: through a person’s identity provider login, or an Access service token for autonomous agents.⁠Source 3, Source 12
Pricing modelConsumption-based per service, with no upfront commitment or minimum fee.⁠Source 13 AWS Agent Registry has a monthly free tier.⁠Source 13Cloudflare says MCP server portals are available to all Cloudflare customers.⁠Source 14 A separate price for portals is not publicly documented.
Generally availableSince October 2025; AWS Agent Registry since August 2026.⁠Source 15Since 24 September 2026.⁠Source 14

What each one is

Amazon Bedrock AgentCore

Amazon Bedrock AgentCore is AWS’s platform for building, deploying, and operating agents with any framework and foundation model.⁠Source 1 Its modular services, usable together or independently, include a serverless Runtime for hosting agents, Gateway, Identity, Policy, Observability, and AWS Agent Registry.⁠Source 1, Source 5, Source 7, Source 8, Source 16, Source 17

Cloudflare MCP server portals

Cloudflare says MCP server portals are part of Cloudflare One, its SASE platform.⁠Source 2 Admins add MCP servers to Cloudflare Access, and a portal puts them behind one URL that MCP clients connect to, with Access policies and request logs.⁠Source 3

The differences that matter

  1. What each one catalogs

    Amazon Bedrock AgentCore

    AWS Agent Registry catalogs agents, MCP servers, tools, and skills; consumers see only records approved through its workflow.⁠Source 5, Source 18

    Cloudflare MCP server portals

    Admins add MCP servers to Cloudflare Access, up to 80 per portal; a portal shows each user only servers whose Allow policy they match.⁠Source 3

    With AWS Organizations, AWS Agent Registry can create records for Runtimes and Gateways it detects in member accounts.⁠Source 19 A portal’s MCP clients can list available servers with a built-in tool.⁠Source 3

  2. Identity and access for agents

    Amazon Bedrock AgentCore

    Agent identities are workload identities; Runtime and Gateway can accept JWTs from any OAuth 2.0 identity provider, and Policy can check each Gateway request.⁠Source 8, Source 16, Source 20

    Cloudflare MCP server portals

    People sign in through their identity provider; autonomous agents can use an Access service token, authorized at the portal and for each server.⁠Source 3, Source 12

    Upstream, AgentCore Gateway handles outbound authentication to tools.⁠Source 7 A portal attaches each server’s credentials, and service token sessions use that server’s admin credential.⁠Source 3

  3. How each one is priced

    Amazon Bedrock AgentCore

    Consumption-based per service, with no upfront commitment or minimum fee; Gateway calls such as InvokeTool are $0.005 per 1,000.⁠Source 13

    Cloudflare MCP server portals

    Cloudflare says MCP server portals are available to all Cloudflare customers.⁠Source 14 A separate price for portals is not publicly documented.

For security teams

What a security review asks, answered from each vendor’s public documentation.

TopicAmazon Bedrock AgentCoreCloudflare MCP server portals
Network exposureGateway can forward to an outside agent’s endpoint URL; VPC-hosted MCP servers and APIs can stay off the public internet.⁠Source 9, Source 21Clients use the portal’s HTTPS URL.⁠Source 3 Private servers can use outbound-only Cloudflare Tunnel; their OAuth authorization servers must be public.⁠Source 3, Source 22
IdentityAgent identities are workload identities.⁠Source 8 Runtime uses IAM SigV4 by default, or JWTs from Cognito, Entra ID, Okta, and others.⁠Source 20, Source 23, Source 24Identity provider or service token.⁠Source 3, Source 12 Blocked users can use a server’s direct URL; Cloudflare advises making Access its OAuth provider.⁠Source 3
Access changes and revocationExplicit deny policies can block Runtime, Gateway, and Memory access; removing an account from a registry share revokes its access.⁠Source 10, Source 25Deleting a service token revokes it.⁠Source 26 A tool turned off in a portal can’t be called through it.⁠Source 3
Audit trailCloudTrail can log Gateway calls (data events are off by default) and logs Registry control-plane calls; Policy logs its decisions.⁠Source 16, Source 19, Source 27, Source 28Access logs individual tool requests, viewable per portal or server.⁠Source 3 Logpush export to storage or SIEM tools: Enterprise plans only.⁠Source 3
ComplianceHIPAA eligible; AWS lists it as FedRAMP (Class C and Class D), SOC 2, ISO 27001:2022, and CSA STAR compliant.⁠Source 29, Source 30Super Administrators can get Cloudflare’s PCI, SOC 2, and ISO documents.⁠Source 31 Their scope for portals is not publicly documented.

Full comparison

18 criteria in five groups. Every cell links to its source, or says no public source answers it.

Amazon Bedrock AgentCore and Cloudflare MCP server portals compared on 18 criteria
Amazon Bedrock AgentCoreCloudflare MCP server portals
What it is
What it is and who it’s forAWS’s platform for building, deploying, and operating agents with any framework and model, for moving agents from proof of concept to production.⁠Source 1, Source 24Cloudflare says portals are part of Cloudflare One, its SASE platform.⁠Source 2 A portal puts multiple MCP servers behind one HTTP endpoint, governed through Access.⁠Source 3, Source 4
MaturityGenerally available since October 2025.⁠Source 15 Policy GA since March 2026; AWS Agent Registry GA since August 2026.⁠Source 15Generally available since 24 September 2026, after an open beta announced on 26 August 2025.⁠Source 14, Source 32 Earlier called Agents Gateway in some contexts.⁠Source 3
Control
Agent registry and discoveryAWS Agent Registry catalogs agents, MCP servers, tools, and skills, on AWS or elsewhere, behind an approval workflow.⁠Source 1, Source 5 Consumers see only approved records.⁠Source 18Admins add MCP servers to Access, up to 80 per portal; portals show users only servers whose Allow policy they match.⁠Source 3 Agent registry: not publicly documented.
Identity and access controlAgent identities are workload identities.⁠Source 8 Runtime defaults to IAM SigV4; Runtime and Gateway can validate JWTs from any OAuth 2.0 identity provider.⁠Source 20, Source 23Sign-in through Access with an identity provider, or an Access service token.⁠Source 3, Source 12 Policies can match emails, groups, country, and device posture.⁠Source 3
Ownership, policy, and revocationGateway policies in natural language or Cedar set which tools an agent may call and when.⁠Source 16 Curators can deprecate registry records to remove them from discovery.⁠Source 19Admins pick each portal’s tools and prompt templates; turned-off tools can’t be called through it.⁠Source 3 Access can auto-disable or delete unused service tokens.⁠Source 26
Audit log and observabilityMetrics, spans, and logs go to CloudWatch.⁠Source 17 CloudTrail can log Gateway calls (data events are off by default) and logs Registry control-plane calls.⁠Source 19, Source 27, Source 28Access logs individual tool requests, viewable per portal or server.⁠Source 3 Exported logs record the user’s email and tool called; Logpush export is Enterprise only.⁠Source 3, Source 33
Connection
How agents connectAgents can run in Runtime, or elsewhere behind a Gateway that forwards to their endpoint URL.⁠Source 1, Source 9 Outbound-only agent connections: not publicly documented.MCP clients connect to the portal’s HTTPS URL, and it proxies each tool call.⁠Source 3 Private servers need Gateway routing and Cloudflare Tunnel or another connector.⁠Source 3
Agents across organizationsRegistries can be shared with other AWS accounts through AWS RAM to discover, publish, or administer.⁠Source 10 Runtime agents can be opened to other accounts.⁠Source 25Cloudflare One can use several identity providers at once when working with partners.⁠Source 34 Federating another organization’s agents: not publicly documented.
Protocol supportRuntime agents can serve HTTP, MCP, A2A, or AG-UI.⁠Source 35 Gateway supports MCP 2026-07-28, 2025-11-25, 2025-06-18, and 2025-03-26 for MCP server targets.⁠Source 36Stateless MCP 2026-07-28 and earlier 2025 Streamable HTTP clients and servers; upstream over Streamable HTTP or SSE.⁠Source 3 A2A support: not publicly documented.
Frameworks, models, and clouds supportedRuntime works with CrewAI, LangGraph, LlamaIndex, Google ADK, OpenAI Agents SDK, Strands Agents, and custom frameworks; Identity covers self-hosted agents.⁠Source 1, Source 11MCP clients that support remote servers can connect.⁠Source 3 Stdio-only servers can’t be added, and some servers reject proxy-based clients like portals.⁠Source 3
Operations
Deployment options and data residencyAWS says cross-region inference can move Memory, Policy, and Evaluations prompts out of the primary Region; AgentCore may store content to improve your service.⁠Source 1, Source 37A portal’s hostname is a proxied CNAME record pointing to gateway.agents.cloudflare.com.⁠Source 3 Self-hosting a portal: not publicly documented.
Compliance attestationsAWS lists AgentCore as FedRAMP (Class C and Class D) compliant.⁠Source 29, Source 30 It is HIPAA eligible, and SOC 2, ISO 27001:2022, and CSA STAR compliant.⁠Source 15, Source 29Super Administrators can get Cloudflare’s PCI, SOC 2, ISO, and other documents in the dashboard.⁠Source 31 Their scope for portals is not publicly documented.
Support and SLAAWS says the Amazon Bedrock SLA applies to AgentCore.⁠Source 24 Basic Support is included for all AWS customers.⁠Source 38Support options vary by Zero Trust plan; professional services are Contract add-ons.⁠Source 39 Cloudflare states a 100% uptime SLA for paid Zero Trust plans.⁠Source 39
Time and effort to get runningThe quickstart needs an AWS account with credentials, plus Node.js 20 or later for the AgentCore CLI.⁠Source 40 It scaffolds, tests, and deploys one agent.⁠Source 40Needs a domain on Cloudflare and an identity provider in Zero Trust.⁠Source 3 Then add MCP servers, create a portal with tools and policies, and connect clients.⁠Source 3
Pricing model and public pricesConsumption-based per service, no minimum fee.⁠Source 13 Gateway: $0.005 per 1,000 calls such as InvokeTool.⁠Source 13 Registry: 5,000 records free monthly, then $0.400 per 1,000.⁠Source 13Cloudflare says MCP server portals are available to all Cloudflare customers.⁠Source 14 A separate price for portals is not publicly documented.
Building
Agent building toolsWrite the agent loop in Python with a framework such as Strands, LangGraph, or Google ADK and deploy it to Runtime, or use the managed Harness.⁠Source 1, Source 40Separately from portals, Cloudflare’s Agents docs cover building and hosting agents, and remote MCP servers can be built on Workers.⁠Source 4, Source 41
Model accessModel-agnostic, AWS says: foundation models in or outside Amazon Bedrock, including OpenAI, Gemini, Claude, Nova, Llama, and Mistral.⁠Source 24Not publicly documented for portals. Cloudflare’s separate Agents SDK has Workers AI built in and works with OpenAI, Anthropic, and Google Gemini.⁠Source 42
Integrations and ecosystemGateway has 1-click integrations with tools such as Salesforce, Slack, Jira, Asana, and Zendesk, and can import AWS Partner tools bought in AWS Marketplace.⁠Source 7, Source 24Portals can be managed with Terraform.⁠Source 3 Cloudflare One supports social, open source, and corporate identity providers.⁠Source 34 Marketplace: not publicly documented.

Which to choose

Choose Amazon Bedrock AgentCore if

  • You want to build, host, and operate agents on one platform, with any framework and foundation model.⁠Source 1
  • You need a catalog of agents as well as tools, where only records approved through a workflow are discoverable.⁠Source 5
  • You want agent identities built on workload identities, with Cedar or natural-language policies checking tool calls through Gateway.⁠Source 8, Source 16
  • Your teams span AWS accounts: a registry shared through AWS RAM lets other accounts discover, publish, or administer records.⁠Source 10

Choose Cloudflare MCP server portals if

  • You want one governed URL for your MCP servers, with Access policies on email, group, country, and device posture.⁠Source 3
  • You run Cloudflare One: Cloudflare says portals are part of it, and they use your Zero Trust identity provider.⁠Source 2, Source 3
  • Your MCP servers are private: portals can reach them through outbound-only Cloudflare Tunnel, with Gateway routing turned on.⁠Source 3, Source 22, Source 43
  • You want tool-level control: admins pick each portal’s tools and prompt templates, and Access logs individual tool requests.⁠Source 3

Questions buyers ask

Does either one keep a registry of agents?

AgentCore does: AWS Agent Registry catalogs agents, MCP servers, tools, and skills, including ones hosted outside AWS.⁠Source 1, Source 5 Admins add MCP servers to Cloudflare Access, and a portal lists the ones available to each user; a registry of agents is not publicly documented for portals.⁠Source 3

Do they support MCP and A2A?

Both support MCP: AgentCore Gateway supports MCP versions including 2026-07-28 for MCP server targets, and portals support stateless MCP 2026-07-28.⁠Source 3, Source 36 AgentCore Runtime can host A2A servers; A2A support in portals is not publicly documented.⁠Source 35, Source 44

How is each one priced?

AgentCore is consumption-based, with no upfront commitment or minimum fee; Gateway calls such as InvokeTool cost $0.005 per 1,000.⁠Source 13 Cloudflare says MCP server portals are available to all Cloudflare customers.⁠Source 14 A separate price for portals is not publicly documented.

Can either one connect agents across organizations?

AgentCore works across AWS accounts: registries can be shared through AWS RAM, even outside your AWS Organization, and Runtime agents can be opened to other accounts.⁠Source 10, Source 25 Cloudflare One can use several identity providers at once for partners; federating another organization’s agents is not publicly documented.⁠Source 34

How we compare

Read the full method

Every claim on this page links to a public source. Where none answers a question, the page says so.

We re-check every fact at least every 90 days. This page was last checked .

Something wrong or out of date? Tell us and we’ll correct it.

Sources

51 public sources, each with the date we checked it. Every one opens in a new tab.

  1. Source 1: Overview - Amazon Bedrock AgentCore (Developer Guide) AWS · checked Back:abcdefghijklmnopq

  2. Source 2: Securing the AI Revolution: Introducing Cloudflare MCP Server Portals Cloudflare · checked Back:abcde

  3. Source 3: MCP server portals · Cloudflare One docs Cloudflare · checked Back:abcdefghijklmnopqrstuvwxyz27282930313233343536373839404142434445

  4. Source 4: MCP governance · Cloudflare Agents docs Cloudflare · checked Back:abcde

  5. Source 5: AWS Agent Registry: Discover and manage agents, tools, and resources AWS · checked Back:abcdefghi

  6. Source 6: Supported targets for Amazon Bedrock AgentCore gateways AWS · checked Back to text

  7. Source 7: Amazon Bedrock AgentCore Gateway: A secure AI gateway for agents, tools, and models AWS · checked Back:abcd

  8. Source 8: Provide identity and credential management for agent applications with Amazon Bedrock AgentCore Identity AWS · checked Back:abcdefg

  9. Source 9: HTTP passthrough targets - AgentCore Gateway AWS · checked Back:abc

  10. Source 10: Sharing a registry across accounts with AWS RAM AWS · checked Back:abcde

  11. Source 11: Features of AgentCore Identity AWS · checked Back:ab

  12. Source 12: Service token support for MCP server portals · Changelog Cloudflare · checked Back:abcd

  13. Source 13: Amazon Bedrock AgentCore Pricing AWS · checked Back:abcdefg

  14. Source 14: MCP server portals are now generally available · Changelog Cloudflare · checked Back:abcdef

  15. Source 15: Release notes - Amazon Bedrock AgentCore AWS · checked Back:abcd

  16. Source 16: Policy in Amazon Bedrock AgentCore: Control Agent Interactions AWS · checked Back:abcde

  17. Source 17: Observe your agent applications on Amazon Bedrock AgentCore Observability AWS · checked Back:ab

  18. Source 18: Concepts and terminology - AWS Agent Registry AWS · checked Back:ab

  19. Source 19: Key capabilities - AWS Agent Registry AWS · checked Back:abcd

  20. Source 20: Configure inbound JWT authorizer AWS · checked Back:abc

  21. Source 21: Connect to private resources in your VPC using VPC Lattice AWS · checked Back to text

  22. Source 22: Cloudflare Tunnel · Cloudflare One docs Cloudflare · checked Back:ab

  23. Source 23: Authenticate and authorize with Inbound Auth and Outbound Auth AWS · checked Back:ab

  24. Source 24: Amazon Bedrock AgentCore FAQs AWS · checked Back:abcde

  25. Source 25: Resource-based policies for Amazon Bedrock AgentCore AWS · checked Back:abc

  26. Source 26: Service tokens · Cloudflare One docs Cloudflare · checked Back:ab

  27. Source 27: Log Amazon Bedrock AgentCore Gateway API calls with CloudTrail AWS · checked Back:ab

  28. Source 28: Enable CloudTrail data event logging for Amazon Bedrock AgentCore Gateway resources - Amazon Bedrock AgentCore AWS · checked Back:ab

  29. Source 29: Compliance validation for Amazon Bedrock AgentCore AWS · checked Back:abc

  30. Source 30: Federal Risk and Authorization Management Program (FedRAMP) - Services in Scope - Amazon Web Services AWS · checked Back:ab

  31. Source 31: Compliance documentation · Cloudflare Fundamentals docs Cloudflare · checked Back:ab

  32. Source 32: MCP server portals · Changelog Cloudflare · checked Back to text

  33. Source 33: MCP Portal Logs · Cloudflare Logs docs Cloudflare · checked Back to text

  34. Source 34: Identity providers · Cloudflare One docs Cloudflare · checked Back:abc

  35. Source 35: Understand the AgentCore Runtime service contract AWS · checked Back:ab

  36. Source 36: MCP servers targets - AgentCore Gateway AWS · checked Back:ab

  37. Source 37: Cross-region inference in AgentCore Memory, Policy in AgentCore, and AgentCore Evaluations AWS · checked Back to text

  38. Source 38: Compare AWS Support plans AWS · checked Back to text

  39. Source 39: Cloudflare Access | Zero Trust Network Access (ZTNA) Cloudflare · checked Back:ab

  40. Source 40: Get started with Amazon Bedrock AgentCore AWS · checked Back:abc

  41. Source 41: Build Agents on Cloudflare · Cloudflare Agents docs Cloudflare · checked Back to text

  42. Source 42: Using AI Models · Cloudflare Agents docs Cloudflare · checked Back to text

  43. Source 43: Private MCP server support for MCP server portals · Changelog Cloudflare · checked Back to text

  44. Source 44: Deploy A2A servers in AgentCore Runtime AWS · checked Back to text

  45. Source 45: Why Blocks? Blocks.ai · checked Back to text

  46. Source 46: What is Blocks? Blocks.ai · checked Back to text

  47. Source 47: Your company's private network Blocks.ai · checked Back to text

  48. Source 48: Network requirements Blocks.ai · checked Back to text

  49. Source 49: Solutions: Agent sprawl Blocks.ai · checked Back to text

  50. Source 50: Solutions: Partner networks Blocks.ai · checked Back to text

  51. Source 51: Pricing Blocks.ai · checked Back to text