GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
Cloud region data for AWS, Azure, GCP, OCI & more. Query by location, compliance, GPU.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"cloud-regions": {
"command": "npx",
"args": [
"-y",
"mcp-server-cloud-regions"
]
}
}
}在终端中运行这条命令
claude mcp add cloud-regions -- npx -y mcp-server-cloud-regions粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"cloud-regions": {
"command": "npx",
"args": [
"-y",
"mcp-server-cloud-regions"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"cloud-regions": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-server-cloud-regions"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 jasonwilbur 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.0.4)于10个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A Model Context Protocol (MCP) server providing comprehensive cloud region data across all major providers. Query, filter, and compare cloud infrastructure locations worldwide.
269 regions across 14 cloud providers — query by location, compliance, sustainability, and GPU availability.
Add to your config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": { "cloud-regions": { "command": "npx", "args": ["-y", "mcp-server-cloud-regions"] } } }
claude mcp add cloud-regions -- npx -y mcp-server-cloud-regions
Then ask Claude questions like:
Planning multi-cloud deployments requires answering questions across providers:
This MCP server provides a unified data model to answer these questions instantly.
| Tier | Providers |
|---|---|
| Hyperscalers | AWS, Azure, GCP, Oracle Cloud (OCI) |
| Major | DigitalOcean, Linode (Akamai), Vultr |
| Specialized | Crusoe (clean energy), CoreWeave (GPU), Lambda Labs (AI/ML), Paperspace (GPU/ML) |
| Regional | OVHcloud, Hetzner, Scaleway |
| Tool | Description |
|---|---|
list_regions | List all regions with filtering (provider, country, compliance, GPU, sustainability, region type) |
get_region | Get detailed info for a specific region by ID (e.g., aws-us-east-1) |
list_providers | List all cloud providers with metadata and tier classification |
get_provider_regions | Get all regions for a specific provider |
search_regions | Full-text search across region names, cities, countries, and provider names |
| Tool | Description |
|---|---|
find_nearby_regions | Find regions nearest to coordinates (for latency optimization) |
list_countries | All countries with cloud presence and region counts |
list_cities | All cities with data centers and which providers operate there |
| Tool | Description |
|---|---|
find_compliant_regions | Filter by certifications (HIPAA, GDPR, FedRAMP, SOC2, PCI-DSS, etc.) |
find_sustainable_regions | Find carbon-neutral data centers |
find_gpu_regions | Find regions with GPU availability (A100, H100, TPU, etc.) |
compare_provider_coverage | Compare provider presence in a country or continent |
| Tool | Description |
|---|---|
get_statistics | Summary stats: totals by provider, country, continent, capabilities |
get_data_info | Data freshness: last updated date, version, source URLs for each provider |
The server tracks different types of cloud regions:
| Type | Description | Examples |
|---|---|---|
commercial | Standard public cloud regions | aws-us-east-1, azure-eastus |
government | Government-restricted regions (GovCloud, IL4+) | aws-us-gov-west-1, azure-usgovvirginia |
sovereign | Data sovereignty regions with separate control planes | azure-germanynorth, oci-eu-frankfurt-2 |
china | China regions (separate operators/partitions) | azure-chinaeast, aws-cn-north-1 |
Filter by region type using list_regions with the regionTypes parameter.
Find HIPAA-compliant regions in the US:
{
"tool": "find_compliant_regions", "certifications": ["HIPAA"], "countryCodes": ["US"] }
Find the 5 nearest GPU regions to London:
{
"tool": "find_nearby_regions", "latitude": 51.5074, "longitude": -0.1278, "limit": 5, "hasGpu": true }
List regions with 3+ availability zones:
{
"tool": "list_regions", "minAvailabilityZones": 3 }
Compare European coverage across hyperscalers:
{
"tool": "compare_provider_coverage", "continent": "europe" }
Find government regions:
{
"tool": "list_regions", "regionTypes": ["government", "sovereign"] }
Check when data was last updated:
{
"tool": "get_data_info" }
Each region includes:
{
id: "aws-us-east-1", provider: "aws", regionCode: "us-east-1", displayName: "US East (N. Virginia)", regionType: "commercial", location: { country: "United States", countryCode: "US", city: "Ashburn", latitude: 39.0438, longitude: -77.4874, continent: "north-america" }, availabilityZones: 6, launchedDate: "2006-08-25", status: "ga", compliance: ["SOC1", "SOC2", "HIPAA", "FedRAMP-Moderate", "PCI-DSS"], sustainability: { renewableEnergyPercent: 100, carbonNeutral: true }, services: { compute: true, kubernetes: true, gpu: true, gpuTypes: ["NVIDIA A10G", "NVIDIA A100", "NVIDIA H100"] }, sovereignty: { dataResidency: "US", dataResidencyGuarantee: true } }
The server automatically fetches the latest region data from GitHub on startup, with fallback to bundled data if offline. Data is verified against official provider documentation:
A weekly GitHub Action checks the provider pages for changes and opens an issue when an update may be needed; the region data is then refreshed and released by a maintainer (the dataset itself is curated, not auto-generated from the provider pages).
npm install mcp-server-cloud-regions
Or run directly with npx:
npx -y mcp-server-cloud-regions
Contributions welcome! To add or update provider data:
src/data/providers.tssrc/data/regions-*.tssrc/data/metadata.tsnpm run build && npm run export-data| Command | Description |
|---|---|
npm run build | Compile TypeScript |
npm run export-data | Export regions to data/regions.json |
npm run check-updates | Check if provider pages have changed |
This data is provided for informational purposes only. Cloud providers frequently add, modify, or deprecate regions and services. Users are responsible for verifying region availability, compliance certifications, and service offerings directly with each cloud provider before making deployment decisions.
While we strive to keep this data accurate and up-to-date, we make no guarantees about completeness or correctness. Always consult official provider documentation for production planning.
MIT