Jina AI MCP Tools
Jina AI MCP-Tools
Ein Model Context Protocol (MCP) Server, der in die Jina AI Search Foundation APIs integriert ist.
Funktionen
Dieser MCP-Server bietet Zugriff auf die folgenden Jina AI APIs:
Web Reader - Extrahiert Inhalte von Webseiten mittels r.jina.ai
Web Search - Durchsucht das Web mittels s.jina.ai oder svip.jina.ai (konfigurierbar über
--search-endpoint)
Related MCP server: Jina Web Search MCP
Voraussetzungen
Jina AI API-Schlüssel (Optional) - Erhalten Sie einen kostenlosen API-Schlüssel unter https://jina.ai/?sui=apikey für erweiterte Funktionen
Node.js - Version 16 oder höher
MCP-Server
Verwendung des stdio-Transports (Standard)
Für lokale Integrationen, die von einem anderen Prozess gestartet werden (z. B. 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"
}
}
}
}Verwendung des HTTP-Transports
Für Remote-Server-Bereitstellungen, die über HTTP zugänglich sind:
Server starten:
# 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 3000Verbindung von MCP-Clients:
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"}'
CLI-Optionen:
--transport- Transporttyp:stdiooderhttp(Standard: stdio)--host- Host/Schnittstelle für die Bindung im HTTP-Modus (Standard:127.0.0.1)--port- HTTP-Server-Port (Standard: 3000, nur für HTTP-Transport)--tokens-per-page- Token pro Seite für die Paginierung (Standard: 15000)--search-endpoint- Zu verwendender Such-Endpunkt:standard(s.jina.ai) odervip(svip.jina.ai) (Standard: standard)--cache-size- Reader-Cache-Größe in URLs (Standard: 50)--help- Zeigt die integrierte CLI-Hilfe an
Proxy-Umgebungsvariablen
Ausgehende HTTP-Anfragen berücksichtigen jetzt standardmäßige Proxy-Umgebungsvariablen. Dies gilt für jina_reader, jina_search und jina_search_vip.
Unterstützte Proxy-Variablen:
HTTP_PROXY,HTTPS_PROXY,ALL_PROXYKleingeschriebene Varianten werden ebenfalls unterstützt:
http_proxy,https_proxy,all_proxyAusschlüsse werden über
NO_PROXY/no_proxyrespektiert
Beispiel:
HTTPS_PROXY=http://proxy.internal:8080 npx jina-mcp-tools --transport stdioVerfügbare Tools
jina_reader
Extrahiert und liest Webseiteninhalte.
Parameter:
url- Zu lesende URL (erforderlich)page- Seitennummer für paginierte Inhalte (Standard: 1)customTimeout- Timeout-Überschreibung in Sekunden (optional)
Funktionen:
Automatische Paginierung für große Dokumente
LRU-Cache (50 URLs) für sofortige nachfolgende Seitenanfragen
GitHub-Datei-URLs werden automatisch in Raw-Content-URLs konvertiert
Versucht zuerst
Accept: text/markdownfür eine gepflegte Positivliste von Markdown-fähigen Dokumenten-/Blog-Hosts und greift bei Abruffehlern oder leeren Antworten aufr.jina.aizurück
jina_search / jina_search_vip
Durchsucht das Web. Gibt teilweise Inhalte zurück; verwenden Sie jina_reader für vollständige Inhalte. Erfordert einen API-Schlüssel.
Das registrierte Tool hängt von --search-endpoint ab:
jina_search→standard(s.jina.ai, Standard)jina_search_vip→vip(svip.jina.ai)
Parameter:
query- Suchanfrage (erforderlich)count- Anzahl der Ergebnisse (Standard: 5)siteFilter- Auf eine bestimmte Domain beschränken (z. B. "github.com")
Lizenz
MIT
Links
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 whole seconds (1-2147483) for slow sites |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, but it discloses nothing about authentication requirements, rate limits, JavaScript rendering, truncation/pagination behavior, or error handling. The presence of customTimeout implies slow sites exist but the description never explains that tradeoff.
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?
It is a single short sentence that is front-loaded with the core action, with zero filler. However, the extreme brevity is under-specification rather than true efficiency for a tool this thin on context.
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?
With no annotations and no output schema, the description must explain what comes back and how pagination and timeouts behave; it does neither. An agent cannot tell whether the response is raw HTML, markdown, or plain text, nor how paginated content is returned.
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 url, page, and customTimeout are each documented in the schema itself; baseline 3 applies. The description adds no extra meaning beyond what the schema already provides.
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 states a specific verb pair (read/extract) and resource (web page), so an agent knows this fetches and parses page content. With no sibling tools to distinguish from, there is nothing more to disambiguate, but it does not clarify output form (markdown vs HTML vs text).
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?
There is no when-to-use guidance, no mention of alternatives, and no conditions under which this tool should be preferred or avoided. The description is purely a statement of function.
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.3.0- Changed
jina_reader8 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - changed
Input schema / properties / customTimeout / descriptionPrevious value: -"Override timeout in seconds for slow sites"New value: +"Override timeout in whole seconds (1-2147483) for slow sites" - added
Input schema / properties / customTimeout / exclusiveMinimumAdded value: +0 - added
Input schema / properties / customTimeout / maximumAdded value: +2147483 - changed
Input schema / properties / customTimeout / typePrevious value: -"number"New value: +"integer" - added
Input schema / properties / page / exclusiveMinimumAdded value: +0 - added
Input schema / properties / page / maximumAdded value: +9007199254740991 - changed
Input schema / properties / page / typePrevious value: -"number"New value: +"integer"
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
There is only one tool, so there is no possibility of confusion or misselection. Its purpose is clearly distinct.
With a single tool named jina_reader, consistency is trivially satisfied. It follows a readable snake_case pattern.
A server branded as 'Jina AI MCP Tools' with only one tool seems too few for the apparent scope. Jina AI typically offers multiple capabilities (search, embeddings, reranking), so one tool feels under-provisioned.
The surface only covers web page reading, with no search, embedding, reranking, or other operations implied by the Jina AI brand. This is a severely incomplete toolset for the stated purpose.
Maintenance
Related MCP Connectors
Jina AI Reader/Search MCP — turn any URL into clean LLM-ready markdown, plus web search.
Web search and page reading for AI agents, including JSON APIs, RSS feeds and YouTube.
Web search, agentic search, news, page retrieval, sitemaps, and trending topics through Search1API.
Web search and page fetch for AI agents. Results come from a shared cache; cached calls cost less.
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.128 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