Connect Google Sheets to Cursor

A lot of early-stage teams keep real source-of-truth data — pricing tiers, feature flags, config values — in a spreadsheet, then hand-copy it into the codebase whenever it changes. Synquil lets Cursor read that spreadsheet directly, so the values in your code can't silently drift from the sheet everyone actually edits.

Google Sheets
Synquil
Synced data layer
Cursor

How it works

  1. Connect Google Sheets. Authorize read access over OAuth and choose which spreadsheets to sync.
  2. Generate an API key. Cursor connects via API key rather than the OAuth connector flow Claude uses — generate one from your Synquil dashboard's API keys section.
  3. Add the MCP config to Cursor. Synquil gives you a ready-to-paste JSON snippet with your endpoint URL and the key already in the right header — drop it into Cursor's MCP settings.
  4. Ask Cursor's agent about the sheet while you code. It queries the synced data directly, in the same chat where you're writing the implementation.

Example questions you can ask Cursor

What are the current plan limits defined in our pricing sheet? I need this for a validation function.
Pull the rows from the 'Feature Flags' sheet so I can scaffold a TypeScript enum.
Check whether this CSV import script matches the column headers in the live sheet.
List every row added to the config sheet since we last deployed.

Where this is most useful

This is built for the specific habit of small teams keeping business logic in a spreadsheet — a pricing tier table, a feature-flag matrix, a limits config — and then implementing it in code by hand. With a synced connection, Cursor's agent can check its own work against the sheet directly, instead of trusting whatever was last copied over.

Let Cursor read your spreadsheet directly.

Connect Google Sheets free