GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者による説明(英語の原文)
Multi-cloud + LLM pricing for AI agents: AWS/Azure/GCP/OCI, RI break-even, TCO, price history.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"cloudprice": {
"command": "uvx",
"args": [
"cloudprice-mcp"
]
}
}
}ターミナルでこれを実行します
claude mcp add cloudprice -- uvx cloudprice-mcpプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"cloudprice": {
"command": "uvx",
"args": [
"cloudprice-mcp"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"cloudprice": {
"type": "stdio",
"command": "uvx",
"args": [
"cloudprice-mcp"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント Albaker-Group で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(0.29.0)がレジストリに届いたのは一昨日です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにPython (uv)も必要です。
同じカテゴリには:GitHub, Desktop Commander, Cloudflare MCP
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況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、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
Ask your AI assistant what the cloud will cost — and get real list prices back.
cloudprice-mcp gives Claude, Cursor, GitHub Copilot and any other MCP client pricing and FinOps tools across AWS, Azure, GCP and OCI, plus LLM token prices for ~2,300 model/provider combinations. No cloud account, no API keys: it works from a catalogue refreshed every week from the providers' public pricing APIs.
Add this to your MCP client's config (Claude Desktop, Cursor, VS Code, …). uvx downloads and runs it — nothing to install first:
{
"mcpServers": { "cloudprice": { "command": "uvx", "args": ["cloudprice-mcp"] } } }
Claude Code: claude mcp add cloudprice -- uvx cloudprice-mcp
Or install with pip and let it configure every client it finds (asks before writing each one):
pip install cloudprice-mcp
cloudprice-mcp setup
Restart the client and the 39 tools appear. Problems? cloudprice-mcp doctor says what is wrong; INSTALL.md has per-client steps for Windows, macOS and Linux. Python 3.10+.
What's new in each release: [CHANGELOG.md](CHANGELOG.md).
*"I run 6× t3.2xlarge on AWS. On-demand vs 1-year Savings Plan vs 3-year RI —
what's the break-even month?"* →
optimize_commitment
*"At 50 TB/month internet egress, which cloud is cheapest, and what would
moving save over 3 years?"* →
compare_egress,find_egress_arbitrage
(OCI ≈ $340/mo vs ≈ $4,000/mo on the hyperscalers)
*"Size this 3-tier app on all four clouds: 8 web (4 vCPU/16 GB), 12 app
(8/32), 4 DB (16/64), 5 TB SSD, 10 TB/month egress, multi-AZ."* →
compare_workload,compare_total_cost_of_ownership
*"Cheapest way to run 50M input / 10M output tokens a month — and is Claude
Sonnet the same price on Bedrock and Vertex?"* →
compare_token_pricing
*"Which H100 instance is cheapest per GPU-hour across the four clouds?"* →
compare_gpu_workload
*"We send 2B input / 500M output tokens a month to an API. Would renting
8×H100 and serving Llama ourselves be cheaper, and at what volume?"* →
compare_llm_vs_selfhost
*"My support agent averages 8 steps with a 2k system prompt and 3k of tool
definitions. What does 50,000 runs a month cost on Sonnet vs Haiku, and how
much does prompt caching save — and hosted on AgentCore or Lambda?"* →
estimate_agent_cost(tokens + AgentCore Runtime/Gateway/Memory vs Lambda)
*"We'll run this agent 50,000 times a month, 30 seconds a run, on Claude
Sonnet. AgentCore, Azure Foundry or Vertex Agent Engine, or just Lambda?"* →
compare_agent_platforms(hosting, tools, memory and tokens on each)
*"What changed in LLM pricing this week — anything cheaper on Bedrock or
Groq?"* →
llm_price_changes(weekly archive of ~3,600 model/provider prices)
*"Which models on Bedrock and Azure OpenAI retire in the next six months,
and what replaces them?"* →
model_retirements(also flagged automatically
by
analyze_ai_spendandreview_agentcore)
*"How has OCI E5.Flex pricing moved since May?"* →
get_price_history
*"Here's our FOCUS export (~/Downloads/focus-2026-10.csv). Where is the money
going, what jumped last month, and how much of our usage do Savings Plans
cover?"* →
analyze_bill— reads the file on your machine; nothing is sent
anywhere, and hosted deployments cannot call it.
*"Using the same export: are we under-committed, what spiked last week, and
how much of our spend is missing a
teamtag?"* →find_commitment_gaps,
detect_bill_anomalies,analyze_cost_allocation
*"What will this month's bill be, and what's our cost per customer? We had
41,000 customers in September and 44,500 in October."* →
forecast_spend,
calculate_unit_cost
*"What would the compute on this bill cost on Azure, GCP or OCI?"* →
reprice_bill: the vCPU and memory you actually used, priced on all four
clouds, next to what you paid
*"What are we spending on Bedrock and Azure OpenAI, are we paying list
price, and would prompt caching help?"* →
analyze_ai_spend
*"Review our AgentCore deployment: is it secure, what does the agent cost,
and what should we fix first?"* →
review_agentcoreon
terraform show -jsonoutput, plus the bill
Every answer carries the catalogue date and an honest_gaps list of what the tool does not model, so the AI can tell you where the number stops being exact.
Nine tools read files on your machine: your cloud bill (a FOCUS export) and your AgentCore deployment (Terraform JSON). The file never leaves your machine; only the tool's summary goes back to your AI assistant. Hosted deployments of this server cannot call these tools at all.
1. Download your bill as a FOCUS CSV. Every major cloud exports it:
| Cloud | Where | Guide |
|---|---|---|
| AWS | Billing and Cost Management → Data Exports → Create → a FOCUS export, CSV → download from the S3 bucket | AWS |
| Azure | Cost Management → Exports → Create → Cost and usage details (FOCUS), CSV → download from the storage account. Big exports arrive in parts; analyse one part or join them first | Azure |
| GCP | Billing → FOCUS export to BigQuery → query the month you want → save the result as CSV | GCP |
| OCI | Billing → Cost and Usage Reports → FOCUS reports → Download | OCI |
.csv and .csv.gz up to 500 MB are read.
2. Ask, with the file path in the question:
*"Here's our bill: ~/Downloads/focus-2026-10.csv. Where is the money going,
what would it cost on the other clouds, and what are we spending on AI?"*
| Question | Tool |
|---|---|
| Where does the money go? | analyze_bill |
| Are we under-committed? What are idle commitments costing? | find_commitment_gaps |
| What spiked, and since when? | detect_bill_anomalies |
How much spend is missing our team tag? | analyze_cost_allocation |
| What will this month cost? Cost per customer? | forecast_spend, calculate_unit_cost |
| What would our compute cost on the other clouds? | reprice_bill |
| What do our AI models cost, and are we paying list price? | analyze_ai_spend |
3. Review an AgentCore deployment (Terraform):
terraform plan -out=tfplan
terraform show -json tfplan > plan.json
*"Review our AgentCore deployment in ~/plan.json. Our bill is
~/Downloads/focus.csv and the agent is tagged agent=support."*
You get findings ranked by severity: public network, unauthenticated gateways, model permissions, secrets in environment variables, idle-session cost, missing alarms and tags, and with the bill, what the agent costs and what caching would save. Each one names the resource, the Terraform fix and the AWS page behind the rule. To accept a finding on purpose, say so: *"skip S1 on aws_bedrockagentcore_agent_runtime.demo, it is a public demo"*. It is then listed as skipped, with your reason.
plan.json holds every value Terraform knows, secrets included. The review never repeats them, but keep the file out of git and delete it when you are done.
39 tools, grouped by job. Full descriptions and arguments: [docs/TOOLS.md](docs/TOOLS.md) (generated from the server, so it is always current).
| Job | Tools |
|---|---|
| Look up one price | get_aws_price, get_azure_price, get_gcp_price, compare_clouds |
| Price a workload | compare_compute_inventory, compare_storage_inventory, compare_workload, compare_object_storage, compare_postgres_database, compare_egress |
| FinOps decisions | assess_migration, optimize_commitment, compare_total_cost_of_ownership, find_egress_arbitrage, generate_decision_report |
| Spot, GPU, carbon | compare_spot, compare_gpu_workload, compare_carbon_footprint |
| Price history | get_price_history, list_tracked_skus, detect_price_anomalies, watch_workload |
| AI / LLM costs | estimate_agent_cost, compare_agent_platforms, compare_llm_vs_selfhost, compare_token_pricing, lookup_extended_model_pricing, llm_price_changes, model_retirements |
| Your actual bill (local only) | analyze_bill, find_commitment_gaps, detect_bill_anomalies, analyze_cost_allocation, forecast_spend, calculate_unit_cost, reprice_bill, analyze_ai_spend |
| Review a deployment (local only) | review_agentcore |
| Export | export_focus |
How the tools map to the FinOps Foundation capabilities. "Your bill" tools read a FOCUS export locally; the rest work from list prices and the weekly price archive.
| Capability | Tools |
|---|---|
| Data ingestion | analyze_bill (FOCUS in), export_focus (FOCUS out) |
| Reporting & analytics | analyze_bill |
| Allocation | analyze_cost_allocation |
| Anomaly management | detect_bill_anomalies (your spend), detect_price_anomalies, watch_workload (list prices) |
| Rate optimization | find_commitment_gaps (your spend), optimize_commitment, compare_spot |
| Workload optimization | compare_compute_inventory, compare_gpu_workload, compare_llm_vs_selfhost |
| Planning & estimating | compare_workload, compare_total_cost_of_ownership, assess_migration, estimate_agent_cost, compare_agent_platforms |
| Architecting for cloud | reprice_bill (your spend), review_agentcore (your config), find_egress_arbitrage, assess_migration |
| Benchmarking | reprice_bill (your spend), compare_clouds, compare_token_pricing, llm_price_changes |
| Cloud sustainability | compare_carbon_footprint |
| Forecasting | forecast_spend |
| Unit economics | calculate_unit_cost |
| FinOps for AI | analyze_ai_spend (your spend), review_agentcore (your agent), model_retirements, estimate_agent_cost, compare_agent_platforms, compare_token_pricing, llm_price_changes |
compare_workload input{
"compute": [ { "name": "web", "vcpus": 4, "memory_gb": 16, "quantity": 8, "os_disk_gb": 100, "os_disk_type": "ssd" }, { "name": "app", "vcpus": 8, "memory_gb": 32, "quantity": 12, "os_disk_gb": 200, "os_disk_type": "ssd" }, { "name": "db", "vcpus": 16, "memory_gb": 64, "quantity": 4, "os_disk_gb": 500, "os_disk_type": "ssd" } ], "storage": [ { "name
冒頭だけを表示しています。続きはリポジトリで読めます