/

/

How to connect GitHub Copilot (VS Code) to your Datadog costs

How to connect GitHub Copilot (VS Code) to your Datadog costs

Connection guide

How to connect GitHub Copilot (VS Code) to your Datadog costs

Connect GitHub Copilot to your Datadog costs through Costory's FinOps MCP. GitHub Copilot gets Datadog spend allocated to teams and features, next to the deploys and metrics that explain it.

What you can ask GitHub Copilot about Datadog

  • “Why did our Datadog bill move this month?”

  • “Correlate the cost spike with Datadog traffic metrics.”

  • “Show Datadog CI spend by pipeline.”

  • “Which team owns most of this month's increase?”

  • “Set up a weekly Slack report of this spend for #finops.”

What GitHub Copilot sees

Costory ingests Datadog cost through Datadog usage and billing estimates (+ metrics and CI Visibility), normalizes it into one cost model alongside your other providers, and allocates it with products, usage types, teams; Datadog metrics next to cost. Through the MCP server, GitHub Copilot can query that allocated cost, compare periods, look up deploys and other events in the same window, and create alerts, reports and dashboards in Costory. It has no write access to your cloud accounts.

Good to know for this setup

  • Copilot in VS Code reads Costory from .vscode/mcp.json, under "servers", with type "http" and the Costory URL. Committing that file shares the setup with the repository.

  • Datadog billing is an estimate until invoiced; compare against usage.

Set up in about 30 minutes

1. Connect Datadog to Costory. Follow the Datadog setup guide in the docs.

2. Map spend to owners. Use Virtual Dimensions to group accounts, projects, labels and tags into teams, products and environments, even where tagging is incomplete.

3. Add Costory to VS Code with GitHub Copilot.

Add Costory to .vscode/mcp.json and use Copilot in agent mode:

{
  "servers": {
    "costory": { "type": "http", "url": "https://app-api.costory.io/mcp" }
  }
}
{
  "servers": {
    "costory": { "type": "http", "url": "https://app-api.costory.io/mcp" }
  }
}
{
  "servers": {
    "costory": { "type": "http", "url": "https://app-api.costory.io/mcp" }
  }
}

No local proxy or Node.js is needed: point the client directly at https://app-api.costory.io/mcp.

Full client instructions: MCP setup guide.

Good to know

Datadog billing is an estimate until invoiced; compare against usage.

Datadog tools compared


Datadog MCP

Costory MCP

Scope

Provider-specific

AWS, GCP, Azure, Kubernetes, data platforms, LLM APIs

Allocation to teams

Not built in

Virtual Dimensions

Deploys and events next to cost

No

Yes (GitHub, CI/CD, custom events)

Actions

Provider-specific

Alerts, reports, dashboards, events in Costory

Based on each tool's public documentation; check current docs before deciding.

FAQ

Does GitHub Copilot get write access to my Datadog account?

No. Costory reads billing data you export to it. MCP actions create Costory objects (alerts, reports, dashboards, events) and never change your cloud resources.

What Datadog permissions does Costory need?

Read access to billing data only. The exact permissions are listed in the Datadog setup guide.

Where is the data stored?

Costory stores and processes data in the EU.

How much does it cost?

Plans start at €250/month (up to €10M annual cloud spend), billed annually, with a 30-day free trial. See pricing.

Connect in under 30 minutes. Get your first optimization recommendation the next day.

30-day free trial. Copilot, €250/month, or Copilot Pro, €1,000/month, billed annually.

First optimization recommendation

The next day

ROI

Pays for itself with the first recommendation you act on

Setup

About 30 minutes

Data residency

EU

Access

Read-only on your cloud