eu-cloud-mcp

An MCP server for moving off AWS, Google Cloud and Azure to EU-owned clouds. Ask your AI assistant or coding agent which EU product replaces a service, what the same setup costs on each cloud, what leaving will cost in egress, and how locked-in your Terraform is. Answers come from open, sourced data maintained by MoveInfra, not from the model's memory.

• Read-only. No cloud credentials. The Terraform scan reads files locally and sends nothing anywhere.

• Current data. Tools read the open data repositories below (cached for an hour), so prices and rules follow the monthly updates without a new release.

• Open source, Apache-2.0. Node.js 20 or later.

Install

Claude Code:

claude mcp add eu-cloud -- npx -y eu-cloud-mcp

Codex (~/.codex/config.toml):

[mcp_servers.eu-cloud]
command = "npx"
args = ["-y", "eu-cloud-mcp"]

Claude Desktop, Cursor, VS Code and other clients (mcpServers JSON):

{
  "mcpServers": {
    "eu-cloud": { "command": "npx", "args": ["-y", "eu-cloud-mcp"] }
  }
}

Related MCP server: CloudCost MCP Server

Examples

• "Which EU cloud replaces our DynamoDB tables, and how much work is it?"

• "What does a 4 vCPU / 16 GB server cost on Hetzner, Scaleway and UpCloud compared with AWS?"

• "We have 40 TB in S3. What will it cost to move it out, and can we get the egress waived?"

• "Scan ./infra and tell me what would be hard to move to an EU-owned cloud."

Data

Found a wrong price or a missing service? Open an issue or PR in the data repository; this server picks it up within an hour.

scan_terraform_lock_in is a quick Terraform-only scan. For CloudFormation, SAM, Serverless, SDK imports, file and line numbers, and a CI check, use cloud-lock-in-scanner.

Development

npm ci
npm test            # tests read the live data
npx @modelcontextprotocol/inspector node index.js

Planning a move? MoveInfra migrates companies from AWS, Google Cloud and Azure to EU-owned clouds.

Releasing

Bump the version in package.json, index.js and server.json, commit, then git tag vX.Y.Z && git push --tags. The release workflow publishes to npm (trusted publishing, no token) and to the MCP registry.