Jina AI MCP Tools
Herramientas MCP de Jina AI
Un servidor de Protocolo de Contexto de Modelo (MCP) que se integra con las API de Jina AI Search Foundation.
Características
Este servidor MCP proporciona acceso a las siguientes API de Jina AI:
Web Reader - Extrae contenido de páginas web usando r.jina.ai
Web Search - Busca en la web usando s.jina.ai o svip.jina.ai (configurable mediante
--search-endpoint)
Related MCP server: Jina Web Search MCP
Requisitos previos
Clave de API de Jina AI (Opcional) - Obtenga una clave de API gratuita en https://jina.ai/?sui=apikey para funciones mejoradas
Node.js - Versión 16 o superior
Servidor MCP
Uso del transporte stdio (Predeterminado)
Para integraciones locales iniciadas por otro proceso (p. ej., Claude Desktop, VS Code, Cursor):
{
"mcpServers": {
"jina-mcp-tools": {
"command": "npx",
"args": [
"jina-mcp-tools",
"--transport", "stdio",
"--tokens-per-page", "15000",
"--search-endpoint", "standard"
],
"env": {
"JINA_API_KEY": "your_jina_api_key_here_optional"
}
}
}
}Uso del transporte HTTP
Para implementaciones de servidor remoto accesibles a través de HTTP:
Iniciar el servidor:
# With API key
JINA_API_KEY=your_api_key npx jina-mcp-tools --transport http --host 127.0.0.1 --port 3000
# Without API key (reader tool only, binds to 127.0.0.1 by default)
npx jina-mcp-tools --transport http --port 3000Conectar desde clientes MCP:
MCP Inspector:
npx @modelcontextprotocol/inspector→http://localhost:3000/mcpClaude Code:
claude mcp add --transport http jina-tools http://localhost:3000/mcpVS Code:
code --add-mcp '{"name":"jina-tools","type":"http","url":"http://localhost:3000/mcp"}'
Opciones de CLI:
--transport- Tipo de transporte:stdioohttp(predeterminado: stdio)--host- Host/interfaz para enlazar en modo HTTP (predeterminado:127.0.0.1)--port- Puerto del servidor HTTP (predeterminado: 3000, solo para transporte HTTP)--tokens-per-page- Tokens por página para paginación (predeterminado: 15000)--search-endpoint- Punto final de búsqueda a utilizar:standard(s.jina.ai) ovip(svip.jina.ai) (predeterminado: standard)--cache-size- Tamaño de caché del lector en URL (predeterminado: 50)--help- Muestra la ayuda integrada de la CLI
Variables de entorno de proxy
Las solicitudes HTTP salientes ahora respetan las variables de entorno de proxy estándar. Esto se aplica a jina_reader, jina_search y jina_search_vip.
Variables de proxy admitidas:
HTTP_PROXY,HTTPS_PROXY,ALL_PROXYTambién se admiten variantes en minúsculas:
http_proxy,https_proxy,all_proxyLas exclusiones se respetan mediante
NO_PROXY/no_proxy
Ejemplo:
HTTPS_PROXY=http://proxy.internal:8080 npx jina-mcp-tools --transport stdioHerramientas disponibles
jina_reader
Extrae y lee el contenido de una página web.
Parámetros:
url- URL a leer (obligatorio)page- Número de página para contenido paginado (predeterminado: 1)customTimeout- Anulación del tiempo de espera en segundos (opcional)
Características:
Paginación automática para documentos grandes
Caché LRU (50 URL) para solicitudes de página posteriores instantáneas
Las URL de archivos de GitHub se convierten automáticamente en URL de contenido sin procesar
Intenta primero
Accept: text/markdownpara una lista de permitidos mantenida de hosts de blogs/documentos compatibles con markdown, luego recurre ar.jina.aien caso de error de recuperación o respuestas vacías
jina_search / jina_search_vip
Busca en la web. Devuelve contenido parcial; use jina_reader para obtener el contenido completo. Requiere clave de API.
La herramienta registrada depende de --search-endpoint:
jina_search→standard(s.jina.ai, predeterminado)jina_search_vip→vip(svip.jina.ai)
Parámetros:
query- Consulta de búsqueda (obligatorio)count- Número de resultados (predeterminado: 5)siteFilter- Limitar a un dominio específico (p. ej., "github.com")
Licencia
MIT
Enlaces
Available Tools
1 tooljina_readerJina Web ReaderC
Read and extract content from web page.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL of the webpage to read and extract content from | |
| page | No | Page number for paginated content (1-indexed) | |
| customTimeout | No | Override timeout in seconds for slow sites |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits such as whether it is read-only, rate limits, or error handling. It implies reading but offers no further context.
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 sentence with no wasted words. However, it is very minimal and could be expanded slightly without losing conciseness.
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?
The tool is simple (read a URL), but the description lacks details about output format, pagination handling (page parameter), or timeout behavior (customTimeout). It is minimally complete but has gaps.
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 baseline is 3. The description adds no additional meaning beyond the schema; it does not explain parameter semantics or usage context.
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 'Read and extract content from web page' clearly states the verb and resource, but lacks specificity about what kind of extraction (e.g., full HTML, text only). With no sibling tools to differentiate, it is adequate.
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?
No guidance on when to use this tool versus alternatives or any exclusions. The description does not mention constraints like authentication requirements or site compatibility.
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.2.4- Changed
jina_reader1 field changed- removed
Input schema / additionalPropertiesRemoved value: -false
1 tool update
v1.2.0- First observed
jina_reader
TDQS
Scored across 1 tool
Only one tool exists, so there is no ambiguity or risk of misselection.
The single tool name follows a clear 'jina_reader' pattern, consistent with common conventions.
One tool is too few for a server named 'Jina AI MCP Tools', which suggests a broader scope; a tool for reading web pages alone feels insufficient.
The server provides only a read operation, lacking obvious complementary tools like search, list, or write operations, resulting in significant gaps for a comprehensive AI tools surface.
Maintenance
Related MCP Connectors
Jina AI Reader/Search MCP — turn any URL into clean LLM-ready markdown, plus web search.
Web search, AI agent, and content extraction via You.com APIs
Web search, news, page retrieval, sitemaps, and trending topics through Search1API.
The best web search for your AI Agent
Related MCP Servers
- AlicenseBqualityFmaintenanceEnables efficient web search integration with Jina.ai's Search API, offering clean, LLM-optimized content retrieval with support for various content types and configurable caching.121 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables web content retrieval and semantic search capabilities through the Jina AI API. Provides tools to fetch content from URLs and perform intelligent web searches with natural language queries.3MIT
- AlicenseNot gradedqualityCmaintenanceProvides web content extraction, search capabilities (web, arXiv, SSRN, images), semantic deduplication, and reranking through Jina AI's Reader, Embeddings, and Reranker APIs.1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides tools for web content extraction, search, embeddings, reranking, and image processing via Jina AI APIs, enabling intelligent data retrieval and analysis.Apache 2.0