Google Patents MCP Server
Servidor MCP de patentes de Google ( google-patents-mcp )
Este proyecto proporciona un servidor de Protocolo de Contexto de Modelo (MCP) que permite buscar información de patentes de Google a través de la API de patentes de Google SerpApi .
Registro de cambios
v0.2.0 (17/04/2025)
Corrección: se implementaron controladores vacíos para los métodos MCP
resources/listyprompts/list.Corrección: Se declaró la capacidad
promptsen la inicialización del servidor.Tarea: Dependencias actualizadas.
Estos cambios tienen como objetivo mejorar la compatibilidad con clientes MCP como Claude Desktop que pueden requerir estos puntos finales estándar, aunque todavía no se han realizado pruebas directas con Claude Desktop.
Related MCP server: Serper MCP Server
Características
Proporciona una herramienta MCP
search_patentspara buscar patentes de Google.Utiliza SerpApi como backend.
Se puede ejecutar directamente usando
npxsin instalación local.
Prerrequisitos
Node.js: se recomienda la versión 18 o superior.
npm: necesario para ejecutar el comando
npx.Clave API de SerpApi: necesita una clave API válida de SerpApi para utilizar la API de patentes de Google.
Inicio rápido (usando npx)
La forma más sencilla de ejecutar este servidor es usar npx . Este comando descarga (si es necesario) y ejecuta el servidor directamente.
npx @kunihiros/google-patents-mcpNota: reemplace @kunihiros/google-patents-mcp con el nombre del paquete publicado real si es diferente.
El servidor se iniciará y escuchará las solicitudes MCP en la entrada/salida estándar.
Configuración
El servidor requiere tu clave API de SerpApi. Puedes proporcionarla de una de las siguientes maneras:
Variable de entorno (recomendada para hosts MCP): Configure la variable de entorno
SERPAPI_API_KEYal ejecutar el servidor. Las configuraciones de host MCP suelen permitir configurar variables de entorno para los servidores.Ejemplo de fragmento de configuración del host MCP (
config.jsono similar):{ "mcpServers": { "google-patents-mcp": { "command": "npx", "args": [ "-y", // Skips confirmation if the package isn't installed locally "@kunihiros/google-patents-mcp" // Use the correct package name ], "env": { "SERPAPI_API_KEY": "YOUR_ACTUAL_SERPAPI_KEY" // Optional: Set log level // "LOG_LEVEL": "debug" } } } }Archivo .env: crea un archivo
.enven el directorio donde ejecuta el comandonpx(para pruebas locales o si no usa un host MCP), o en tu directorio de inicio (~/.google-patents-mcp.env), con el siguiente contenido:SERPAPI_API_KEY=YOUR_ACTUAL_SERPAPI_KEY # Optional: Set log level (e.g., debug, info, warn, error) # LOG_LEVEL=debugNota: Si bien usar un archivo
.enves conveniente para pruebas locales, para producción o integración con hosts MCP, configurar la variable de entorno directamente a través de la configuración del host es el enfoque recomendado y más seguro. El principal caso de uso previsto es la ejecución mediantenpx, donde las variables de entorno suelen ser administradas por el proceso de llamada o el host MCP.
El servidor busca archivos .env en el siguiente orden: * ./.env (relativo a dónde se ejecuta npx ) * ~/.google-patents-mcp.env (en su directorio de inicio)
Herramienta MCP proporcionada
search_patents
Busca patentes de Google a través de SerpApi.
Esquema de entrada:
{
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "Search query (required). Although optional in SerpApi docs, a non-empty query is practically needed. Use semicolon (;) to separate multiple terms. Advanced syntax like '(Coffee) OR (Tea);(A47J)' is supported. See 'About Google Patents' for details."
},
"page": {
"type": "integer",
"description": "Page number for pagination (default: 1).",
"default": 1
},
"num": {
"type": "integer",
"description": "Number of results per page (default: 10). **IMPORTANT: Must be 10 or greater (up to 100).**",
"default": 10,
"minimum": 10,
"maximum": 100
},
"sort": {
"type": "string",
"enum": ["relevance", "new", "old"],
"description": "Sorting method. 'relevance' (default), 'new' (newest by filing/publication date), 'old' (oldest by filing/publication date).",
"default": "relevance"
},
"before": {
"type": "string",
"description": "Maximum date filter (e.g., 'publication:20231231', 'filing:20220101'). Format: type:YYYYMMDD where type is 'priority', 'filing', or 'publication'."
},
"after": {
"type": "string",
"description": "Minimum date filter (e.g., 'publication:20230101', 'filing:20220601'). Format: type:YYYYMMDD where type is 'priority', 'filing', or 'publication'."
},
"inventor": {
"type": "string",
"description": "Filter by inventor names. Separate multiple names with a comma (,)."
},
"assignee": {
"type": "string",
"description": "Filter by assignee names. Separate multiple names with a comma (,)."
},
"country": {
"type": "string",
"description": "Filter by country codes (e.g., 'US', 'WO,JP'). Separate multiple codes with a comma (,)."
},
"language": {
"type": "string",
"description": "Filter by language (e.g., 'ENGLISH', 'JAPANESE,GERMAN'). Separate multiple languages with a comma (,). Supported: ENGLISH, GERMAN, CHINESE, FRENCH, SPANISH, ARABIC, JAPANESE, KOREAN, PORTUGUESE, RUSSIAN, ITALIAN, DUTCH, SWEDISH, FINNISH, NORWEGIAN, DANISH."
},
"status": {
"type": "string",
"enum": ["GRANT", "APPLICATION"],
"description": "Filter by patent status: 'GRANT' or 'APPLICATION'."
},
"type": {
"type": "string",
"enum": ["PATENT", "DESIGN"],
"description": "Filter by patent type: 'PATENT' or 'DESIGN'."
},
"scholar": {
"type": "boolean",
"description": "Include Google Scholar results (default: false).",
"default": false
}
},
"required": ["q"]
}Producción:
Devuelve un objeto JSON que contiene los resultados de búsqueda de SerpApi. La estructura sigue el formato de respuesta de SerpApi.
Ejemplo de uso (solicitud MCP):
{
"mcp_version": "1.0",
"type": "CallToolRequest",
"id": "req-123",
"server_name": "google-patents-mcp",
"params": {
"name": "search_patents",
"arguments": {
"q": "organic light emitting diode",
"num": 10,
"language": "ENGLISH",
"status": "GRANT",
"after": "publication:20230101"
}
}
}Desarrollo
Clonar el repositorio (si es necesario para el desarrollo):
# git clone <repository-url> # cd google-patents-mcpInstalar dependencias:
npm installCree un archivo
.env: copie.env.examplea.envy agregue suSERPAPI_API_KEY.Construir:
npm run buildEjecutar localmente:
npm startO para desarrollo con reconstrucción automática:
npm run dev
Explotación florestal
Los registros se envían al error estándar.
El nivel de registro se puede controlar mediante la variable de entorno
LOG_LEVEL(error,warn,info,http,verbose,debug,silly). El valor predeterminado esinfo.Se intenta crear un archivo de registro en la raíz del proyecto (
google-patents-server.log), el directorio de inicio del usuario (~/.google-patents-server.log) o/tmp/google-patents-server.log.
Licencia
Licencia MIT (Ver archivo LICENCIA)
Available Tools
1 toolsearch_patentsC
Searches Google Patents using SerpApi. Allows filtering by date, inventor, assignee, country, language, status, type, and sorting.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Minimum date filter (e.g., 'publication:20230101', 'filing:20220601'). Format: type:YYYYMMDD where type is 'priority', 'filing', or 'publication'. | |
| assignee | No | Filter by assignee names. Separate multiple names with a comma (,). | |
| before | No | Maximum date filter (e.g., 'publication:20231231', 'filing:20220101'). Format: type:YYYYMMDD where type is 'priority', 'filing', or 'publication'. | |
| country | No | Filter by country codes (e.g., 'US', 'WO,JP'). Separate multiple codes with a comma (,). | |
| inventor | No | Filter by inventor names. Separate multiple names with a comma (,). | |
| language | No | Filter by language (e.g., 'ENGLISH', 'JAPANESE,GERMAN'). Separate multiple languages with a comma (,). Supported: ENGLISH, GERMAN, CHINESE, FRENCH, SPANISH, ARABIC, JAPANESE, KOREAN, PORTUGUESE, RUSSIAN, ITALIAN, DUTCH, SWEDISH, FINNISH, NORWEGIAN, DANISH. | |
| num | No | Number of results per page (default: 10). **IMPORTANT: Must be 10 or greater (up to 100).** | |
| page | No | Page number for pagination (default: 1). | |
| q | Yes | Search query (required). Although optional in SerpApi docs, a non-empty query is practically needed. Use semicolon (;) to separate multiple terms. Advanced syntax like '(Coffee) OR (Tea);(A47J)' is supported. See 'About Google Patents' for details. | |
| scholar | No | Include Google Scholar results (default: false). | |
| sort | No | Sorting method. 'relevance' (default), 'new' (newest by filing/publication date), 'old' (oldest by filing/publication date). | relevance |
| status | No | Filter by patent status: 'GRANT' or 'APPLICATION'. | |
| type | No | Filter by patent type: 'PATENT' or 'DESIGN'. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions filtering and sorting but omits critical details like rate limits, authentication needs, pagination behavior, error handling, or response format. For a search tool with 13 parameters, this is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core purpose and enumerates key capabilities without redundancy. Every word serves a purpose, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex search tool with 13 parameters, no annotations, and no output schema, the description is incomplete. It lacks behavioral context, usage guidelines, and details on results or errors, leaving significant gaps for agent understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents all 13 parameters. The description adds no additional parameter semantics beyond listing filter types, which are already covered in schema descriptions. Baseline 3 is appropriate as the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Searches Google Patents') and resource ('patents'), and mentions the service provider ('using SerpApi'). It lists key filtering capabilities, making the purpose specific and actionable. However, without sibling tools, it cannot differentiate from alternatives, preventing a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or typical use cases. It lists filtering options but lacks context on optimal scenarios or limitations, leaving the agent without usage direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
search_patents
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or confusion between tools. The single tool has a clear, distinct purpose focused on searching patents.
The single tool name 'search_patents' follows a consistent verb_noun pattern. Since there is only one tool, naming consistency is inherently perfect with no deviations to assess.
A single tool for a patents server feels thin and under-scoped. While search is a core function, the domain suggests potential for additional operations like retrieving patent details, analyzing trends, or filtering by categories, making the count too low for the apparent scope.
The tool surface is severely incomplete for a patents domain. It only provides search functionality, with obvious gaps such as retrieving full patent documents, getting metadata like citations or legal status, or managing saved searches, which limits agent workflows and causes dead ends.
Maintenance
Related MCP Connectors
Official SerpApi MCP server for Google, Bing, and other search engines.
A Model Context Protocol server for Wix AI tools
MCP server for Google search results via SERP API
Google SERP, Maps, Shopping, News and AI-answer data for AI agents, from the Searlo search API.
Related MCP Servers
- AlicenseBqualityCmaintenanceA Model Context Protocol server that provides Google Jobs search capabilities through SerpAPI integration, featuring multi-language support, flexible search parameters, and rich job details.114 npm23MIT
- FlicenseCqualityCmaintenanceA Model Context Protocol server that enables LLMs to perform Google searches via the Serper API, allowing models to retrieve current information from the web.1339-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to perform web searches using Google Search API, returning up to 20 search results in JSON format.2Apache 2.0
- AlicenseAqualityCmaintenanceMCP server for patent search and prior art discovery powered by Google Patents public dataset on BigQuery. Supports searching patents, fetching full patent details with CPC codes and citations, and retrieving legal claims text.36MIT