Google Sheets and MCP from Python

Do you want to build a server, or use one?

If you want to build a Google Sheets MCP server in Python, the MCP Python SDK plus gspread will get you there — you define tools, authenticate to Google, and run the process. Do this when you need custom tools or write access.

If you want to use one, you do not need Python at all: MCP clients take a URL. But Python is often how you consume the same data outside the agent, and PasteSheet serves the identical rows over plain HTTP.

Reading the same sheet from Python

The endpoint your agent queries over MCP is also a REST API. No client library, no credentials:

import requests

rows = requests.get(
    "https://pastesheet.com/api/your-endpoint-id",
    params={"status": "shipped", "sort": "-date", "limit": 50},
).json()

for row in rows["data"]:
    print(row["customer"], row["total"])

What building it yourself actually costs

The MCP part is the easy half — the SDK is pleasant and a few tools is not much code. The expensive half is Google: a Cloud project, the Sheets API enabled, a service account and its JSON key, and then quota management.

That quota is the part people underestimate. Google allows 300 read requests per minute per project and 60 per minute per user, then returns a 429 (published limits). Agents are chatty — one question becomes a schema read plus several queries — so a naive server hits this quickly, and now you are writing a cache too.

What it costs

MCP is included on the Free plan. Connect any public endpoint over MCP with no Google Cloud project and no credit card. Private endpoints and the account-wide workspace server need a paid plan (from Starter ($9/mo)) for the keys and OAuth they authenticate with.

Pro adds full-text search and aggregation (count, sum, avg, group_by) that your AI agent can call through query_rows.

Frequently asked questions

Sources

• Authorize requests — Google Sheets API — Google
• Usage limits — Google Sheets API — Google

Related guides