WEB RESEARCH / Jina AI
Jina AI Remote MCP Server
Hosted endpoint for Jina's Reader, search, embeddings and reranker APIs, with server-side tool filtering through URL query parameters.
“A remote Model Context Protocol (MCP) server for the Jina Reader, Search, Embeddings and Reranker APIs”
01 / THE REASONING
Why this made the selection.
- Published in Jina AI's own repository; the README at this commit documents the hosted endpoint https://mcp.jina.ai/v1 and a table of 12 tools that marks which need a Jina API key.
- The README documents server-side filtering (include_tools, exclude_tools, include_tags, exclude_tags, max_tokens) applied before tool registration, so a client loads only the tool schemas it asks for.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- README.md at 5d6eb191a75d8e67b6e01ce427f0cc5c05c800aa
- LICENSE at the same commit
- package.json at the same commit
Our findings
- The README says the older /sse endpoint is kept for backward compatibility and that /sse and /v1 both use Streamable HTTP, not the deprecated SSE transport.
- The README's first configuration block marks the Authorization header optional with an inline comment; the example here is that block without the comment, which is not valid JSON.
- read_url arrays cap at 5 entries; a read with a question gets a 60-second budget against 30 seconds for a plain read.
Not established by this review
- Any call to https://mcp.jina.ai/v1
- Tool filtering parameters
- Local wrangler deployment
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Nothing is installed for the hosted server. Add https://mcp.jina.ai/v1 as a remote HTTP server, with an Authorization bearer header carrying a Jina API key when the tools need one. The README's Claude Code command spans two lines and is not reproduced here.
- Clients without remote support use the mcp-remote proxy shown in the README. Do not commit the key.
Before you start
- A Jina API key for search, rerank, deduplication and PDF extraction tools
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"jina-mcp-server": {
"url": "https://mcp.jina.ai/v1",
"headers": {
"Authorization": "Bearer ${JINA_API_KEY}"
}
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Jina AI MCP README ↗Checked
https://github.com/jina-ai/MCP/blob/5d6eb191a75d8e67b6e01ce427f0cc5c05c800aa/README.md
Supports: Hosted endpoint, Tool table and key requirements, Tool filtering, Removed tools, Failure modes
- Jina AI MCP LICENSE ↗Checked
https://github.com/jina-ai/MCP/blob/5d6eb191a75d8e67b6e01ce427f0cc5c05c800aa/LICENSE
Supports: Apache License 2.0
- Jina AI MCP package.json ↗Checked
https://github.com/jina-ai/MCP/blob/5d6eb191a75d8e67b6e01ce427f0cc5c05c800aa/package.json
Supports: Cloudflare Workers project jina-mcp 1.10.0