
Google BigQuery Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_XL1CHYzMkCvLxlGLPBzLHDOTg35sqGtg0BPtLGTY/mcpConnecting Google BigQuery to Lovable
About a minute, in the Connectors catalog
- 1Open Connectors, select the + button in the top right of the catalog, and choose MCP server.
- 2Name the server and paste your Google BigQuery link as the Server URL. The link above is the URL.
- 3Choose No authentication and click Add server, then ask Lovable something real. Google BigQuery is now part of Lovable.
{
"mcpServers": {
"google-bigquery-mcp": {
"url": "https://edge.vinkius.com/vk_preview_XL1CHYzMkCvLxlGLPBzLHDOTg35sqGtg0BPtLGTY/mcp"
}
}
}Lovable + Google BigQuery
One chat. Your Google BigQuery, live inside Lovable.
Real prompts, answered with live data. This is the kind of conversation you will have in Lovable once the connector is in.
Waiting for input…
Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.
These prompts ship with the Google BigQuery Connector. Once yours is connected, they work in your sessions.
The full capability set, the prompts and the observed latency live on the Google BigQuery Connector page.
Mission Control
See everything your Lovable agents do in Google BigQuery.
When Lovable runs a tool in Google BigQuery, it happens on Lovable's side: you see the result in the chat, but not the request itself, what data it carried, or whether a rule was broken.
Now every move lands on your screen.
Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.
Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.
AI Agents Activities
last 30 daysRequest Volume & Latency
requests latencyEvery request your Lovable agents make through Google BigQuery is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your Google BigQuery workflows.
What sets us apart
It's not just the Connector that stays safe. Everything your agents do through it is.
Connecting Google BigQuery to your AI is step one. But an open line between your agents and Google BigQuery is only half the story: without protection, every action they take runs unguarded.
That's why protection doesn't stop at the door.
Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.
Tamper Proof Activity Log
Every request your agents make in Google BigQuery is recorded and signed, so any change to the history becomes detectable.
Automatic Key Rotation
We rotate security keys every 24 hours. Your Google BigQuery connection stays protected without any manual work.
Spending Protection
We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your Google BigQuery actions never surprise you.
Isolated Sandbox
Every execution through Google BigQuery runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.
Security Event Streaming
Security events flow to Splunk, Datadog or your own webhook, so Google BigQuery activity lands in the tools you already rely on.
Instant Resume
Idle connections resume in 3 to 5 ms while preserving their state, keeping your Lovable sessions responsive.
Malicious File Protection
We detect compressed files designed to exhaust system resources and block them before they ever reach Google BigQuery.
Credential Validation
We test your Google BigQuery credentials before saving them. Invalid credentials are rejected instead of being stored.
Separate Usage Limits
Usage stays isolated per account, so activity in one connection never consumes another account's allowance.
One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.
These guarantees are not add-ons: they are the infrastructure every Google BigQuery connection runs on. Read how our infrastructure protects everything your Lovable agents do, end to end.
Inside Vinkius
Get Google BigQuery ready for your AI. It's easy.
You choose Google BigQuery from the Vinkius Catalog, sign in to your Google BigQuery account, and get one connection link. That's it.
You choose Google BigQuery
You find Google BigQuery in the Catalog and install the Connector with one click.
Google BigQuery
Active
Enable ConnectorActivating…You sign in
You connect your Google BigQuery account and choose what you want your AI to access. Your credentials stay encrypted and separate from your AI.
Configure Credentials
Configure credentials for {{connectorName}}
RequiredEncryptedSave & ContinueYou add the link in Lovable
Vinkius gives you one connection link. In Lovable, you add a custom MCP server in the Connectors catalog with the link as the Server URL.
Token generated successfully
MCP Connection URL
https://edge.vinkius.com/vk_preview_XL1CHYzMkCvLxlGLPBzLHDOTg35sqGtg0BPtLGTY/mcpGo to DashboardConnection Token
vk_live_••••••••
Set it up once. Use Google BigQuery with the AI you already use.
FAQ
Lovable access questions.
- 01
Does this work in my published apps?
No. Custom MCP connectors are personal chat connectors: they work in your Lovable chat while it builds for you, but visitors can't reach the tool through your published app.
- 02
If I connect Google BigQuery to Gemini, can I use the same connection in Claude or ChatGPT later?
Yes, and that's the point: the connection is yours, not Gemini's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and Google BigQuery is already there.
- 03
What does Lovable need to connect to Google BigQuery?
Just the link. Choose No authentication as the auth option, because the hosted Connector handles access on our side. If you prefer OAuth, pick it and you'll be prompted to authorize.
- 04
What can I actually ask Gemini to do with Google BigQuery?
Whatever the Connector covers: check data, run actions and bring answers back. The Connector page lists every capability your AI gains, with real examples you can copy.
- 05
Gemini doesn't show the Connector. What do I check?
Make sure the Server URL was pasted exactly as copied and the connector is authorized, then confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.
- 06
Can I remove the access later?
Remove the connector in Connectors and it's out of your chats. Your Vinkius account keeps the connection and its history either way, ready for the next AI.
More questions about Google BigQuery? The Connector page answers them. See everything the Google BigQuery Connector can do
About the Connector
What Google BigQuery adds to your AI.
Once you connect it, your AI gains 7 capabilities: the exact actions it can take in Google BigQuery when you ask. The Connector page lists every one of them in detail, alongside the latency we measure in production and prompts worth trying first.
See everything the Google BigQuery Connector can do