Connect Buron to Claude Code

This walkthrough gets the Buron MCP server running in Claude Code and proves the connection with a live query. By the end, you'll have asked Claude Code a question about your ad data and gotten a real answer back.

You'll need a Buron account with a team that has Google Ads connected. If you haven't done that yet, head to Connect your Google Ads account first.

Set up with the CLI

If you've already installed the Buron CLI, run setup in your project folder:

buron setup

When it asks "Add the Buron MCP server to your editor?", say yes. The CLI writes the MCP config into .claude/settings.local.json for you.

If you haven't installed the CLI yet, install it first:

npm install -g buron

Sign in

Restart Claude Code (or run /mcp to refresh servers). The first time it connects, your browser opens to sign in. Approve the connection and return to your terminal. You won't need to sign in again until the session expires.

Prove it works

Start a new conversation and ask something about your ad data:

What's my total spend and ROAS for the last 7 days?

The agent calls the Buron MCP server, runs a query against your Google Ads account, and returns the numbers. If you see real data, the connection is working.

Try a dashboard

Ask the agent to run one of your dashboards:

Run the overview dashboard for the last 30 days

The agent calls runDashboard and returns your KPIs, charts, and detail tables, the same data you'd see in the Buron dashboard, right in your editor.

Set up manually

If you'd rather skip the CLI, you can add the MCP server directly. Copy your MCP server URL from Settings in Buron, then run in Claude Code:

/mcp add-json buron

Paste this configuration with your URL:

{
  "type": "streamable-http",
  "url": "https://app.buron.ai/api/mcp?teamId=<your-team-id>"
}

What's next

Now that the connection is live, you can:

• File your first launch to capture a code change as a Buron source
• Query ad performance with ad-hoc GAQL or saved reports
• Read and write knowledge files from your team's knowledge layer