PasteSheet

No. You can paste a sheet shared with anyone who has the link, or connect your Google account and choose a restricted sheet in Google Picker. PasteSheet only reads the selected sheet and never writes to it. The source and endpoint are separate choices: keep the endpoint public for keyless reads, or protect it with a bearer key on a paid plan.

Not your own. Public sheets need only a share URL. For a restricted sheet, connect your Google account and choose the exact file in Google Picker; PasteSheet handles the connection and reads that file without asking you to create a Cloud project, OAuth client, service account, or Google API key.

Rows are cached, so an edit appears once the cache expires. The default TTL is 5 minutes; paid plans can tune it anywhere from 30 seconds to 1 hour depending on whether you care more about freshness or about speed. You can also refresh an endpoint by hand at any moment to push a change through immediately, and a manual refresh does not count against your monthly request quota.

Yes. Every endpoint is also a Model Context Protocol (MCP) server, so you can connect it to Claude, ChatGPT, Cursor, or any MCP client and the agent queries your sheet as a native tool — it can list tabs, read the column schema, and filter rows. MCP is included on every plan, including the free one. There is nothing extra to deploy: the endpoint you already have is the MCP server.

No. PasteSheet is read-only by design and never writes back to your spreadsheet. The MCP server exposes exactly three tools — list tabs, get schema, query rows — and none of them can create, edit, or delete anything. That is a deliberate difference from account-connection tools like Google's own MCP or Zapier, where an agent granted access to your sheet can overwrite your source of truth.

The endpoint keeps serving, but the shape of the JSON changes with your sheet — which is exactly how a spreadsheet-backed API breaks a live site silently. PasteSheet snapshots your column schema on every read and compares it against the last known one, so on a paid plan you get an email or webhook alert the moment a column is renamed, added, or dropped. You can also lock the schema, which makes the endpoint fail loudly rather than quietly serve the wrong shape.

Yes — the free plan gives you 3 endpoints and 2,000 requests a month, with MCP included, no credit card, and no expiry. It is a real free tier meant to run a small site or a personal agent, not a trial that stops working after a fortnight. You only need a paid plan when you want more endpoints, more traffic, private endpoints, a custom cache TTL, or schema alerts.

Requests over your plan's monthly cap get a clear 429 response telling you to upgrade or wait until next month — not a blank page or a silent failure. The quota resets on the calendar-month boundary.

No — they're independent. The rate limit is short-burst protection (60–5,000 requests/min depending on plan); the monthly quota is your total usage for the month. You can be well under your monthly quota and still get throttled if you fire too many requests in one minute.

No. Manually refreshing a sheet's cached data is separate from serving API/MCP reads, so it doesn't consume your monthly request quota.