Half the data I need while coding does not live in the repo. Seed rows, the pricing table, a small feature-flag list, the copy a non-technical teammate owns. All of it sits in a Google Sheet, and every time the editor's agent needed a value from it I was tabbing over, copying a block of cells, and pasting it into the chat. That works once. By the fourth time it is just a tax on getting anything done.
The fix is to let the editor read the sheet itself. MCP, the Model Context Protocol, is the standard way an AI client connects to an outside data source: the server hands the agent a small set of tools, and the agent decides when to call them. VS Code, Cursor, and Windsurf all speak it natively, so none of them need a plugin or a local process to talk to one.
What they do need is a server to point at. PasteSheet takes a Google Sheet you have shared with "Anyone with the link" and hosts it as an MCP endpoint, which is just a URL a client can connect to. There is no Google Cloud project, no OAuth consent screen, and no service-account JSON. This post is that URL dropped into all three editors, plus the one difference between their config files that cost me twenty minutes.
One URL, three config files
