Skip to content

Connect BigQuery to Codex

  • Can I rerun this in CI?

Have Codex use your BigQuery data to check the export for missing days, then rerun it any time with codex exec. Lemonado connects them in about 1 minute, no API keys needed.

MCPhttps://mcp.lemonado.io/mcp

Why connect BigQuery to Codex?

Codex runs in your terminal, its IDE extension and scripts, so what it finds once can be rerun with codex exec instead of redone by hand. Connected through Lemonado, it reads your BigQuery GA4 events, datasets, tables and scheduled queries, so it can check the export for missing days with today's numbers.

  • All your BigQuery data

    Datasets and tables your account can read, ready to ask about.

  • Always today's numbers

    Google Ads and Search Console bulk exports, if you run them, synced from BigQuery automatically, so answers use today's numbers.

  • Connect all your tools

    Questions like "What did paid sessions earn?" use BigQuery and GA4, Snowflake at once.

How to connect BigQuery to Codex

Before you start

  • A Google BigQuery account you can sign in to
  • Codex installed
  • A Lemonado account (the free trial works)
  1. 1

    Connect Google BigQuery in Lemonado

    In Lemonado, open Connectors, find Google BigQuery and sign in. Sign in with a Google account that can read the dataset holding your GA4 export, and pick that project. The BigQuery Data Viewer and Job User roles are enough.

  2. 2

    Turn on external access

    In the company's settings, open External tools, turn the connection on, choose which sources it can reach and copy the server URL.

    text
    https://mcp.lemonado.io/mcp
  3. 3

    Add Lemonado to your config

    Add this to ~/.codex/config.toml.

    toml
    [mcp_servers.lemonado]
    url = "https://mcp.lemonado.io/mcp"
  4. 4

    Log in

    Run the login command and finish the sign-in in your browser.

    bash
    codex mcp login lemonado
  5. 5

    Ask Codex about BigQuery

    Run codex mcp list, or /mcp inside Codex, to see the server and its tools. Try "Pull last week's BigQuery numbers, save them to data/bigquery-weekly.csv and give me the codex exec command to refresh it." Or ask: "Save sessions by source" or "Which events never arrive?"

What can Codex do with BigQuery?

Codex reads your BigQuery data from your terminal and turns one-off questions into commands you can rerun with codex exec.

Codex logoCodex

Pull last week's BigQuery numbers, save them to data/bigquery-weekly.csv and give me the codex exec command to refresh it.

Saved data/bigquery-weekly.csv. Run the same prompt with codex exec in a scheduled job and the file refreshes with each week's numbers.

Source: Google BigQuery + your code

Reading this as an AI agent?

Everything an agent needs to set this up, in plain text. Paste this page's link into Codex and ask it to connect you, or copy the block.

For agents · markdown
# Connect Google BigQuery to Codex (Lemonado MCP)

- Server URL: https://mcp.lemonado.io/mcp
- Transport: Streamable HTTP
- Auth: OAuth; the user signs in to Lemonado in the browser. No API keys.
- In Lemonado: connect the Google Cloud project. Sign in with a Google account that can read the dataset holding your GA4 export, and pick that project. The BigQuery Data Viewer and Job User roles are enough.
- In Codex: ~/.codex/config.toml

```toml
[mcp_servers.lemonado]
url = "https://mcp.lemonado.io/mcp"
```

If you are Codex, run the setup yourself:

Add the Lemonado MCP server to my Codex config. Append this to ~/.codex/config.toml:
[mcp_servers.lemonado]
url = "https://mcp.lemonado.io/mcp"
Then run codex mcp login lemonado so I can sign in, and check that codex mcp list shows it. Once I've signed in, list the Google BigQuery accounts Lemonado can reach.

First question to try: "Pull last week's BigQuery numbers, save them to data/bigquery-weekly.csv and give me the codex exec command to refresh it."

More: https://lemonado.io/integrations/bigquery · https://lemonado.io/llms.txt
FAQ

Frequently Asked Questions

Yes, through Lemonado. Connect your Google Cloud project in Lemonado, add Lemonado in ~/.codex/config.toml, and Codex can check the export for missing days with your live data.

Yes. Google's BigQuery MCP server is hosted, so Codex can use it too. It covers Google BigQuery only. Lemonado covers Google BigQuery plus your ad platforms, GA4 and the rest of your stack in one connection, so Codex can answer questions across them.

Run codex mcp list. If lemonado shows as not logged in, run codex mcp login lemonado again. In Lemonado, check that Google BigQuery is connected and External tools is on for the company. If yesterday's GA4 data is missing, the daily export may not have landed yet. GA4 writes the events_ table for a day several hours after it ends.

Yes, if both are connected in Lemonado. One connection reaches every source you allow, so you can ask things like "Join GA4 purchase revenue from BigQuery with Google Ads cost by campaign for last month."

MCP is included in Lemonado's paid plans and in the free trial, so you can try it before you pay.

See plans and pricing

Still have a question?

Shoot us an email at hello@lemonado.io.

Try for free

Stop fighting with data. Start feeding your AI.

Connect your data to AI and free your team from reporting and busywork.

Try Lemonado free