Launching today
PasteSheet
Google Sheet → JSON API + MCP server, instantly
6 followers
Google Sheet → JSON API + MCP server, instantly
6 followers
Paste a Google Sheet URL and get a live JSON REST API and MCP server in seconds. No backend, no deploy, no code. The same endpoint works for REST calls, AI agents (Claude, Cursor, ChatGPT), and an embeddable search widget. Unlike other sheet-to-API tools, PasteSheet gives you MCP out of the box, schema drift alerts, and a free tier that tells you when you're close to the limit — instead of silently returning blank pages.
Hey PH 👋
I built PasteSheet because a Google Sheet at my day job kept going blank.
We had a FAQ + reviews sheet wired to a third-party spreadsheet-to-API service. It worked fine — until their free tier silently hit its request cap and started returning empty pages. The fix? Rotating four accounts by hand to dodge the limit.
That was embarrassing enough to build a real solution.
What PasteSheet does:
Paste a public Google Sheet URL → get a live, cached JSON REST API in seconds. No database, no backend, no deploy. The same sheet is also queryable by AI agents (Claude, Cursor, ChatGPT) through an MCP server — using the exact same query engine.
It's built for three kinds of people:
Indie devs & makers — want a backend without standing one up
No-code builders — their spreadsheet already is their database
AI / agent builders — wiring live sheet data into LLMs via MCP
What's free, forever:
3 endpoints, 2,000 requests/month, no credit card, no expiry.
What I'm most proud of:
Being one of the first sheet-to-API tools with native MCP support — the same endpoint that serves your REST calls also works with Claude, Cursor, and ChatGPT out of the box.
Curious how schema drift alerts actually trigger in practice, do you monitor the sheet for changes or does the user need to re-paste the URL for it to detect new columns?
@glersamurmxp9
Good question, it is actually a two-different approach.
On active sheets: every time your sheet's cache refreshes, PasteSheet snapshots the schema in the background and compares it against the last saved one. If it detects a rename, removal, or type change it fires the alert immediately as part of that same cycle. So for sheets getting regular traffic the detection frequency is tied to your cache TTL, down to 30 seconds on paid plans.
On idle sheets: there is a scheduled command that proactively queues schema checks for sheets that have not been fetched recently. So even if nobody is hitting your endpoint, PasteSheet still catches drift and alerts you. It does not wait for organic traffic to trigger the check.
If schema lock is on it goes a step further. Instead of just alerting you, the API starts returning 409 so your app fails loudly instead of silently serving wrong data from a column that no longer exists.
Pasted one of my messy Airtight-style sheets in and it just worked. The MCP setup alone saved me an afternoon of fiddling, and the limit warning is honestly underrated.
@slapugu Glad that it work!
The schema drift alerts are a really thoughtful touch, that kind of thing usually bites you weeks later when something silently breaks. nice to see it surfaced up front instead of buried in a changelog.
@yasinxqdl haha yeah been there, you only add that kind of thing after it bites you once 😅
There's also a schema lock if you want it to just hard fail the moment something changes. No more "wait when did this break"