Google Patents MCP MCP Server

Google Patents MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. # Google Patents MCP Server (google-patents-mcp) [![smithery.

What you get

• Provides an MCP tool search_patents to search Google Patents
• Uses SerpApi as the backend
• Can be run directly using npx without local installation

Setting it up

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Google Patents MCP is connected, these are the calls the assistant has available:

• Fix — ** Implemented empty handlers for resources/list and prompts/list MCP methods
• Chore — ** Updated dependencies
• Node.js — ** Version 18 or higher is recommended
• search_patents — Returns a JSON object containing the search results from SerpApi. The structure follows the SerpApi response format

Configuration and credentials

You will need 3 environment variables: SERPAPI_API_KEY, LOG_LEVEL, YOUR_ACTUAL_SERPAPI_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js: Version 18 or higher is recommended. * npm: Required to run the npx command. * SerpApi API Key: You need a valid API key from SerpApi to use the Google Patents API.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the google patents mcp mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Google Patents MCP's toolset — Fix, Chore, Node.js and 1 more — is a fair guide to whether it matches your workflow. It is maintained by KunihiroS; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.