BigQuery MCP by InsightfulPipe MCP server

BigQuery MCP Server by Insightful Pipe

Connect BigQuery to AI assistants: datasets, schemas and SQL on Google Cloud.

Part of the Insightful Pipe MCP Server Collection — use BigQuery from Claude, ChatGPT, Cursor, and other AI assistants through the Model Context Protocol (MCP).

MCP Server URL

https://bigquery.insightfulmcp.com/

What is BigQuery MCP?

BigQuery MCP is a remote Model Context Protocol server hosted by InsightfulPipe. Query BigQuery datasets, list tables, inspect schemas, and run SQL on your connected Google Cloud projects. The roles you grant the service account in GCP decide whether the connection is read-only or read & write.

Installation

Claude

1. Copy the MCP Server URL: https://bigquery.insightfulmcp.com/
2. Open Claude Connectors Settings
3. Scroll to the bottom and click Add custom connector
4. Paste the URL and click Add
5. Click Connect and sign in to InsightfulPipe if asked. Claude then lists the connector as connected.

ChatGPT

Custom MCP servers are added through ChatGPT's Developer mode. Availability depends on your ChatGPT plan, and workspace admins may need to allow it.

1. Turn on Developer mode in ChatGPT settings
2. Create a new app for a remote MCP server and paste the URL: https://bigquery.insightfulmcp.com/
3. Sign in to InsightfulPipe if asked. The connection finishes as soon as you are signed in.

See OpenAI's guide: Developer mode and MCP apps in ChatGPT

Claude Code

claude mcp add --transport http bigquery https://bigquery.insightfulmcp.com/

Cursor

Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "bigquery": {
      "url": "https://bigquery.insightfulmcp.com/"
    }
  }
}

When Cursor shows Needs authentication, click Connect and sign in to InsightfulPipe if asked.

Available Actions

5 actions: 4 read, 1 write.

Read Actions (4)

Write Actions (1)

Control What Your AI Can Do

You decide what AI agents can do with each connected account:

• Turn individual actions on or off for every connected account, so agents only see the actions you allow.
• Connect as Read-only or Read & Write. A read-only connection can only enable read actions.
• Destructive actions stay off by default. Actions such as deletes are disabled until an admin enables them.
• Team access per account. Restricted team members only use the accounts they are granted, with the read actions enabled on them.

Usage Examples

"List the datasets in my project"

"Show the schema of the events table"

"Run a query for daily sessions over the last 30 days"

Pricing

Shortened. The full README is on GitHub.