Skip to main content
Glama
PsychArch

Jina AI MCP Tools

by PsychArch

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

  1. Jina AI API-Schlüssel (Optional) - Erhalten Sie einen kostenlosen API-Schlüssel unter https://jina.ai/?sui=apikey für erweiterte Funktionen

  2. 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 3000

Verbindung von MCP-Clients:

  • MCP Inspector: npx @modelcontextprotocol/inspectorhttp://localhost:3000/mcp

  • Claude Code: claude mcp add --transport http jina-tools http://localhost:3000/mcp

  • VS Code: code --add-mcp '{"name":"jina-tools","type":"http","url":"http://localhost:3000/mcp"}'

CLI-Optionen:

  • --transport - Transporttyp: stdio oder http (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) oder vip (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_PROXY

  • Kleingeschriebene Varianten werden ebenfalls unterstützt: http_proxy, https_proxy, all_proxy

  • Ausschlüsse werden über NO_PROXY / no_proxy respektiert

Beispiel:

HTTPS_PROXY=http://proxy.internal:8080 npx jina-mcp-tools --transport stdio

Verfü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/markdown für eine gepflegte Positivliste von Markdown-fähigen Dokumenten-/Blog-Hosts und greift bei Abruffehlern oder leeren Antworten auf r.jina.ai zurü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_searchstandard (s.jina.ai, Standard)

  • jina_search_vipvip (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

Available Tools

1 tool
jina_readerJina Web ReaderC

Read and extract content from web page.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the webpage to read and extract content from
pageNoPage number for paginated content (1-indexed)
customTimeoutNoOverride timeout in seconds for slow sites

TDQS

C2.9/5.0
Behavior2/5

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.

Conciseness4/5

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.

Completeness3/5

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.

Parameters3/5

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.

Purpose4/5

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.

Usage Guidelines2/5

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. 1 tool updatev1.2.4
    • Changedjina_reader1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
  2. 1 tool updatev1.2.0
    • First observedjina_reader

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no ambiguity or risk of misselection.

Naming Consistency5/5

The single tool name follows a clear 'jina_reader' pattern, consistent with common conventions.

Tool Count2/5

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.

Completeness2/5

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

ActivitySlowing
ResponsivenessResponsive

Related MCP Connectors

Related MCP Servers

  • A
    license
    B
    quality
    F
    maintenance
    Enables 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.
    1
    21 npm
    3
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables 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.
    3
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Provides web content extraction, search capabilities (web, arXiv, SSRN, images), semantic deduplication, and reranking through Jina AI's Reader, Embeddings, and Reranker APIs.
    1
    Apache 2.0