Azure FinOps MCP Server vs Terraform MCP Server

A side-by-side look at the Azure FinOps MCP Server and Terraform MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Azure FinOps MCP Server logoAzure FinOps MCP ServerCloud Platforms · Local subprocess (stdio)Azure FinOps MCP: cost, budgets, forecasting and optimization for Claude, VS Code and Cursor.48FairAuth: not declaredTerraform MCP Server logoTerraform MCP ServerCloud Platforms · Remote HTTP/SSEThe official Terraform MCP Server seamlessly integrates with the Terraform ecosystem, enabling provider discovery, module analysis, and direct Registry API integration for advanced Infrastructure as Code workflows.79GreatAuth: api key required

Verdict: choose Azure FinOps MCP Server for cloud platforms work as a local process; choose Terraform MCP Server for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Azure FinOps MCP Server logoChoose Azure FinOps MCP Server when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: AZURE_ALLOWED_SUBSCRIPTIONS, AZURE_DEFAULT_SUBSCRIPTION.
  • You want tools like list_subscriptions, get_cost_summary, get_cost_by_dimension.
Explore Azure FinOps MCP Server

Terraform MCP Server logoChoose Terraform MCP Server when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: API key required.
Explore Terraform MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAzure FinOps MCP Server logoAzure FinOps MCP ServerTerraform MCP Server logoTerraform MCP Server
CategoryCloud PlatformsCloud Platforms
Quality signal48/100 · Fair79/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsAZURE_ALLOWED_SUBSCRIPTIONSAZURE_DEFAULT_SUBSCRIPTIONNone listed
Verified ownerCommunity listing Verified
GitHub stars01,553
Directory activity 0 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools14Not listed

Tools & capabilities

Azure FinOps MCP Server tools 14

  • list_subscriptionsList allowed subscriptions with friendly names
  • get_cost_summaryTotal cost for a date range (single sub)
  • get_cost_by_dimensionCost breakdown by service / RG / location / meter
  • get_cost_by_tagCost grouped by tag value (showback/chargeback)
  • get_month_to_date_costCurrent-month spend (single sub)
  • get_portfolio_month_to_date_costCurrent-month spend across ALL subs
  • get_budget_statusBudget consumption for a single sub
  • get_portfolio_budget_statusBudget status across ALL subs
  • find_idle_resourcesUnattached disks, stranded IPs/NICs, stopped VMs
  • find_idle_resources_portfolioIdle resources across ALL subs
  • get_advisor_recommendationsAzure Advisor cost recs with annual savings
  • get_vm_utilizationCPU stats to validate rightsizing
  • +2 more on the listing page

Terraform MCP Server tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Azure FinOps MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "azure-finops-mcp-server": {
      "command": "uvx",
      "args": [
        "azure-finops-mcp"
      ],
      "env": {
        "AZURE_ALLOWED_SUBSCRIPTIONS": "YOUR_AZURE_ALLOWED_SUBSCRIPTIONS_HERE",
        "AZURE_DEFAULT_SUBSCRIPTION": "YOUR_AZURE_DEFAULT_SUBSCRIPTION_HERE"
      }
    }
  }
}

Terraform MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "hashicorp-terraform-mcp-server": {
      "url": "http://localhost:8080/mcp"
    }
  }
}

Frequently asked questions

Azure FinOps MCP Server is categorized under Cloud Platforms and uses a local stdio subprocess. Terraform MCP Server belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Azure FinOps MCP Server for cloud platforms work and Terraform MCP Server for cloud platforms.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Azure FinOps MCP Server has no declared pricing — check the project's own site. Terraform MCP Server is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add azure-finops-mcp-server and hashicorp-terraform-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Azure FinOps MCP Server has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Terraform MCP Server has 79/100 (Great) with 3 views, 0 installs and 1,553 GitHub stars.