Zoho MCP with Amazon Bedrock: UK/EU Data Residency Architecture

Model Context Protocol Architecture: Zoho CRM MCP Server with Amazon Bedrock for UK/EU Data Residency

Model Context Protocol (MCP) works on a Client-Host-Server architecture, where an AI client or host application, such as Claude Desktop or a custom orchestration layer, connects directly to tools via MCP Servers and sends prompts to a model hosted through Amazon Bedrock. For organisations with UK or EU data residency requirements, this architecture can be configured so that both your CRM data and your AI model inference stay within your chosen region throughout.

How the Architecture Fits Together

  • The MCP Client acts as the orchestrator, whether that's Claude Desktop, a custom application, or an AWS-based agent.
  • Amazon Bedrock provides the Claude model execution engine, strictly within a UK or EU region.
  • The Zoho CRM MCP Server exposes CRM schema and queries to the client via OAuth.

Key Requirements for UK/EU Data Residency and Security

1. Host Claude via Amazon Bedrock in a UK/EU Region

Rather than calling Anthropic's public API directly, route your prompts to a Claude model hosted within Amazon Bedrock in an EU region, such as Dublin or Frankfurt, or the London region where available.

On model choice: Which specific Claude model to use, and its exact regional availability on Amazon Bedrock, both change over time as Anthropic and AWS roll out new releases. Rather than naming a specific model version here, check the current Amazon Bedrock model catalogue and its supported regions directly at the time you're implementing this, so you're building against what's actually available rather than a model that may since have been superseded.
  • Data sovereignty. Your prompts and context data sent to Claude stay inside your designated AWS region and VPC perimeter.
  • No training on your data. AWS states that model inputs and outputs processed through Bedrock are not used to train the underlying models.

2. Secure the Zoho MCP Server

Zoho offers official MCP servers, including a Data Insights server for read-only analytics and a Data Operations server for full CRUD access.

  • Data location. Ensure your Zoho CRM instance is hosted on the European domain (zoho.eu), keeping your CRM data stored in EU data centres.
  • Authentication. Access is gated via OAuth 2.0 with scoped user credentials.
  • Enterprise security gateway option. If you use Amazon Bedrock AgentCore Gateway, the Zoho MCP server can be registered as an enterprise target behind AWS IAM and OAuth policies, giving you fine-grained access control, logging via AWS CloudTrail, and API monitoring, all inside your existing AWS cloud security perimeter.

Implementation Options

Depending on how your team actually accesses Claude, one of two setup patterns generally fits.

Option A: Local or Desktop Client

Suited to tools like Claude Desktop or Cursor:

  1. Set up your client's MCP configuration file with the Zoho CRM MCP Server credentials.
  2. Configure the client's LLM provider settings to point to Amazon Bedrock using your AWS credentials and chosen region, rather than an Anthropic API key.

Option B: Enterprise or Cloud Web Application

  1. Use Amazon Bedrock AgentCore Gateway to register the Zoho CRM MCP target securely.
  2. Build a custom internal chat frontend or orchestration layer using an appropriate agent development framework.
  3. The application queries Claude on Bedrock, which decides when to trigger Zoho MCP tools to retrieve CRM data, all within the session boundaries you've configured.
Need help? 1 Cloud Consultants can help you architect a UK/EU-compliant Zoho MCP setup using Amazon Bedrock, including choosing the right implementation pattern for your team. Book a discovery call with 1 Cloud Consultants.