Google Patents MCP Server: Setup and Options

Q: What is google-patents-mcp?

A community MCP server by KunihiroS, published on npm as @kunihiros/google-patents-mcp. It has one tool, search_patents, which calls SerpApi's Google Patents API with your SerpApi key. Its last release, 0.2.0, came out on 2025-04-17.

Q: How do I add Google Patents to Claude Code?

Add SerpApi's server with claude mcp add --transport http serpapi https://mcp.serpapi.com/mcp --header "Authorization: Bearer YOUR_SERPAPI_API_KEY", then ask Claude to search Google Patents. It uses the search tool with engine: google_patents.

Q: Can it read a patent's full claims?

Yes. The google_patents_details engine returns the claims, citations, family and legal events for one patent, given an ID like patent/US11734097B1/en. The full description comes back as a separate link rather than in the response.

On this page

Google Patents MCP Server: Which One to Use and How to Set It Up (Nov 2026)

Google doesn't make a Google Patents MCP server. The one called google-patents-mcp is a community package that searches Google Patents through SerpApi, and it hasn't had a release since April 2025. The maintained route to the same data is SerpApi's official MCP server, using its google_patents engine. TrustedMCP grades it C.

The C isn't about neglect: SerpApi's server shipped two releases this month and has no advisories. It comes from how you sign in, with one account-wide API key and no scopes, and from a hosted endpoint that also answers on plain http://.

How we checked: on 2026-11-07 we read the READMEs, source and package metadata for every Google Patents MCP server we could find on GitHub, npm, PyPI and the MCP Registry, SerpApi's Google Patents and Google Patents Details API docs and pricing page, and the hosted server's unauthenticated handshake and tool list. We didn't install or run any of them, and we didn't spend any SerpApi searches.

Which Google Patents MCP server do people mean?

Several servers use the name. They get their data from one of two places: SerpApi, a paid service that returns Google Patents search results as JSON, or Google Patents Public Datasets on BigQuery, Google's own copy of the patent data that you query with SQL.

Server	Data source	Latest activity	Notes
SerpApi MCP Server (`serpapi/serpapi-mcp`)	SerpApi	v2.2.0, 2026-11-04	Official, MIT, hosted or local. Every SerpApi engine, Google Patents included. Graded C.
`KunihiroS/google-patents-mcp`	SerpApi	npm 0.2.0 on 2025-04-17, last commit 2025-08-25	The one that matches the name. One tool, `search_patents`. MIT, one maintainer.
`mcp-server-google-patents` (PyPI)	SerpApi	0.1.6 on 2025-12-09	Two tools, `search_patents` and `get_patent_details`. No source repo or author named on PyPI.
`kuchtgpt-svg/google-patents-details-mcp`	SerpApi	one commit, 2026-10-03	Fetches one full patent record; meant to sit next to `google-patents-mcp`.
`tushariitr-19/patents-mcp`	BigQuery	last commit 2026-06-19	Go. Three tools: search, patent details, claims. You build it from source.
`sapientsai/patents-mcp-server`	USPTO, EPO and BigQuery	npm 1.2.3 on 2026-10-28	45 tools, 4 of them on BigQuery. One maintainer.

Only the SerpApi server is in our directory. We list the best-maintained option for a keyword, and the others are either a year or more without a release, a few weeks old, or one-person projects with a handful of stars. We'll grade one of them if it becomes the default people reach for.

Why we point you to SerpApi's server instead of google-patents-mcp

google-patents-mcp calls the same SerpApi Google Patents API. If you're going to need a SerpApi key either way, SerpApi's own server gives you the same search plus full patent records, from a company, with changes from several contributors. Three things in the older package also put us off:

No release in over 18 months. npm 0.2.0 dates from 2025-04-17. The last commits (2025-08) only changed the Dockerfile.
It prints debug lines to stdout at startup. The published 0.2.0 build starts with five console.log lines. The MCP spec says, for stdio, "The server MUST NOT write anything to its stdout that is not a valid MCP message." Some clients skip lines that aren't JSON; others report errors. Issue #1 on the repo described JSON errors in Claude Desktop. We read the code; we didn't run it.
The README and the code disagree. The README says it reads a .env file from the folder you run it in or from your home folder; the source says that was removed and only the SERPAPI_API_KEY environment variable counts. It also writes a log file next to the package, or to ~/.google-patents-server.log.

If you already use it and it works for you, the key it holds is the same SerpApi key, so the main risk is that nobody is fixing it.

How to set up SerpApi's MCP server for Google Patents

You need a SerpApi account and API key from your SerpApi dashboard. Connecting and listing tools works without a key; searches don't.

Use the Authorization header wherever your client allows it. The server also accepts the key inside the URL (/YOUR_KEY/mcp), but SerpApi's own README warns that a key in the URL "can appear in request logs". And check the address starts with https://: the hosted server also answers on plain http:// without redirecting you.

Claude Code (from the README):

claude mcp add --transport http serpapi https://mcp.serpapi.com/mcp --header "Authorization: Bearer YOUR_SERPAPI_API_KEY"

Claude Desktop. The simplest option is the MCP Bundle: download serpapi-mcp-2.2.0.mcpb from the latest release and open it with Claude Desktop. It asks for your key, stores it as a sensitive setting, and runs the server on your machine over stdio, talking to serpapi.com directly. The README also shows a hosted config for claude_desktop_config.json, with the key in the URL:

{
  "mcpServers": {
    "serpapi": {
      "type": "http",
      "url": "https://mcp.serpapi.com/YOUR_SERPAPI_API_KEY/mcp"
    }
  }
}

Cursor and VS Code. The README's "Install in Cursor" and "Install in VS Code" buttons add this server entry, with the key in a header:

{
  "type": "http",
  "url": "https://mcp.serpapi.com/mcp",
  "headers": { "Authorization": "Bearer YOUR_SERPAPI_API_KEY" }
}

You can also self-host it (git clone, then uv sync && uv run src/server.py). Be aware it listens on 0.0.0.0:8000 over plain HTTP by default, so keep it on a trusted machine or set MCP_HOST=127.0.0.1. The package isn't on PyPI or npm. More on client setup in our Claude Code MCP setup guide and on keeping keys out of shared files in MCP API keys and config.

How to search Google Patents from Claude, Cursor or VS Code

The server has one main tool, search, that takes SerpApi's parameters for any engine. For Google Patents, set engine to google_patents. You can ask in plain words ("find US patents on solid-state battery electrolytes filed since 2020") and the model fills in the parameters. A call looks like this (our example, built from SerpApi's docs):

{"name": "search", "arguments": {"params": {
  "engine": "google_patents",
  "q": "(solid state battery);(electrolyte)",
  "after": "priority:20200101",
  "country": "US,WO",
  "status": "GRANT",
  "num": 10,
  "output": "md"
}}}

Useful Google Patents parameters, per SerpApi's docs:

Parameter	What it does
`q`	The query. Separate terms with `;`. Google Patents syntax like `(Coffee) OR (Tea);(A47J)` works.
`before`, `after`	Date limits as `type:YYYYMMDD`, where type is `priority`, `filing` or `publication`.
`inventor`, `assignee`	Names, separated by commas.
`country`, `language`	Codes like `US,WO,JP`; languages like `ENGLISH,GERMAN`.
`status`, `type`	`GRANT` or `APPLICATION`; `PATENT` or `DESIGN`.
`litigation`	`YES` or `NO`, for patents with or without known litigation.
`num`, `page`, `sort`	10 to 100 results per page; `sort` is `new` or `old` (default is relevance).
`scholar`	`true` adds Google Scholar results.

For one patent's full record, use the google_patents_details engine with a patent_id such as patent/US11734097B1/en:

{"name": "search", "arguments": {"params": {
  "engine": "google_patents_details",
  "patent_id": "patent/US11734097B1/en"
}}}

That returns the abstract, claims, classifications, inventors and assignees, dates, family and priority links, patent and non-patent citations, cited-by, similar documents and legal events. The full description isn't in the response; it comes as a separate description_link.

Patent records are long. Set "output": "md" to get Markdown back, which SerpApi says cuts token use by about half on average, or "mode": "compact" to drop metadata from JSON. See why MCP tools eat your context window.

What Google Patents searches cost

The MCP server is free. Searches aren't: each Google Patents search or details lookup counts as one search on your SerpApi plan. Per SerpApi's pricing on 2026-11-07:

Free plan: 250 searches a month, up to 50 an hour.
Starter: $25 a month for 1,000 searches.
Cached, errored and failed searches don't count.

An agent doing a prior-art sweep can page through results and open dozens of records in one task, so a free plan goes fast. Ask the agent to say how many searches it plans before it starts.

The BigQuery route: Google's own patent data, with SQL

If you'd rather not pay per search, Google publishes patent data as Google Patents Public Datasets on BigQuery: worldwide bibliographic data and US full text, in tables such as patents-public-data.patents.publications. Google has archived its example-code repo for the dataset; the repo is read-only now, separate from the data itself.

You don't need a patent-specific server to query it. Google's hosted BigQuery MCP server (graded B) runs SQL against any dataset your Google account can read, and MCP Toolbox for Databases can do the same. The trade-offs: you need a Google Cloud project, the model has to write SQL, and broad full-text searches are expensive in data scanned. The sapientsai README estimates a broad full-text search across the dataset scans 200 to 300 GB. BigQuery gives a free monthly query allowance, then charges by data scanned.

tushariitr-19/patents-mcp and the BigQuery tools in sapientsai/patents-mcp-server wrap this same dataset in ready-made search tools, so the model doesn't write SQL.

Other patent MCP servers

If you need US prosecution history, PTAB proceedings or office actions rather than Google's search, a USPTO server fits better. riemannzeta/patent_mcp_server is the most-starred patent MCP server we found (85 stars, commits on 2026-11-01). It uses USPTO's Patent Public Search, the Open Data Portal and the PTAB API, and covers trademarks too. sapientsai/patents-mcp-server adds EPO data, including INPADOC families and legal status across about 44 offices. We haven't graded either.

Is the Google Patents MCP server safe to use?

For reading public patents, the risks are small but real:

Your key is account-wide. Anyone with it can spend your searches. There are no scopes. Keep it out of shared config files and out of URLs.
Patent text is untrusted input. Search results and records go straight into the model's context. A crafted patent abstract or a page fetched with the extract tool could carry instructions. See MCP prompt injection.
Your queries go to SerpApi. SerpApi's README says the hosted server stores no queries or results, only request metrics, and each search goes to serpapi.com. If your search terms describe an unfiled invention, treat them as confidential and read SerpApi's privacy policy first. The MCP Bundle skips mcp.serpapi.com, but the searches still go to serpapi.com.
Results aren't legal advice. Google Patents legal status and "similar documents" are a starting point for a search, not a freedom-to-operate opinion.

All four tools are marked read-only. Searches don't change anything in your SerpApi account beyond using credits.

Common Google Patents MCP errors

Error	Likely cause	Fix
"Missing API key"	No header or key in the URL	Add `Authorization: Bearer YOUR_KEY`, or reinstall the bundle with your key
"Invalid key"	Typo or rotated key	Check it on your SerpApi dashboard
"Rate limit exceeded"	Hourly or monthly plan limit	Wait, or move to a bigger plan
No results	Query too narrow, or wrong date format	Drop filters; dates must be `type:YYYYMMDD`
JSON errors at startup with `google-patents-mcp`	Its debug lines on stdout	Switch to SerpApi's server; see MCP server not working

Need patent search wired into your own tools, with your own sources and limits? We build custom MCP servers.

Why SerpApi's MCP server grades C

We graded SerpApi's open-source MCP server and the hosted endpoint at mcp.serpapi.com. SerpApi's search API itself isn't part of the grade.

Check	Points	Why
Authentication	10 of 30	The only sign-in is your account-wide SerpApi API key, in a header or the URL. No scopes, no OAuth.
Maintenance	25 of 25	Releases on 2026-11-03 and 2026-11-04, with changes from three people merged in the last 60 days.
Known CVEs	25 of 25	No advisories in the repo, the GitHub database or OSV.
Transport	6 of 20	HTTPS works, but the hosted server also serves MCP on plain HTTP with no redirect and no HSTS, and self-hosting defaults to plain HTTP on every interface.

Using the header and an https:// URL takes care of most of what the grade warns about. If SerpApi redirects plain HTTP to HTTPS, the transport points go up; if it adds scoped keys or OAuth, so does the grade. See the SerpApi MCP Server listing and how TrustedMCP scores servers.

Frequently asked questions

Is there an official Google Patents MCP server?

No. Google doesn't publish one. The options are community servers that use SerpApi, SerpApi's own MCP server, or Google's patent data on BigQuery through a BigQuery MCP server.

What is google-patents-mcp?

A community MCP server by KunihiroS, published on npm as @kunihiros/google-patents-mcp. It has one tool, search_patents, which calls SerpApi's Google Patents API with your SerpApi key. Its last release, 0.2.0, came out on 2025-04-17.

Is the Google Patents MCP server free?

The servers are free and open source, but SerpApi isn't: its free plan covers 250 searches a month, and paid plans start at $25 for 1,000. The BigQuery route has a free monthly query allowance, then charges by data scanned.

How do I add Google Patents to Claude Code?

Add SerpApi's server with claude mcp add --transport http serpapi https://mcp.serpapi.com/mcp --header "Authorization: Bearer YOUR_SERPAPI_API_KEY", then ask Claude to search Google Patents. It uses the search tool with engine: google_patents.

Can it read a patent's full claims?

Yes. The google_patents_details engine returns the claims, citations, family and legal events for one patent, given an ID like patent/US11734097B1/en. The full description comes back as a separate link rather than in the response.

Can I use it for a freedom-to-operate or prior-art search?

As a first pass, yes: it's quick at finding candidates by keyword, assignee, CPC code and date. It isn't a substitute for a search by a patent professional, and you should confirm legal status with the patent office itself.

Google Patents MCP or a USPTO MCP server?

Google Patents covers many countries in one search. A USPTO server such as riemannzeta/patent_mcp_server goes deeper on US filings: prosecution history, office actions and PTAB. Many people use one of each.

Does google-patents-mcp still work?

It may, but nobody is fixing it: its last release, 0.2.0, came out on 2025-04-17. The published build prints debug lines to stdout at startup, which some clients report as JSON errors. SerpApi's own MCP server uses the same SerpApi key and is maintained.

Can I search Google Patents without a SerpApi key?

Yes, through Google Patents Public Datasets on BigQuery. Google's hosted BigQuery MCP server or MCP Toolbox for Databases can run SQL against it. You need a Google Cloud project, and BigQuery charges by data scanned after a free monthly allowance.