← Back to directory
J

Jina AI Remote MCP Server

Official
Jina AI's official remote MCP server for web reading, search, and embeddings/reranking
GitHub source repository ↗
★ 830 Stars Category · Other Very popular Source revision 96147b1db939
64FMRS · C
Reliability
7/20
Security and permissions
13/20
Maintenance
12/20
Documentation
18/20
Setup experience
14/20

An officially maintained remote MCP server from Jina AI wrapping its Reader, Embeddings, and Reranker APIs into a broad toolset for web reading, search, deduplication, reranking, and PDF extraction, with server-side tool filtering to manage context usage and thorough documentation covering setup and troubleshooting across major MCP clients.

Read the FMRS scoring method →

An officially maintained remote Model Context Protocol server from Jina AI that exposes 22 tools backed by the Reader, Embeddings, and Reranker APIs — covering URL-to-markdown extraction, web/image/arXiv/SSRN search, screenshotting, deduplication, classification, reranking, and PDF structure extraction. It is hosted at https://mcp.jina.ai/v1 using Streamable HTTP transport (the /sse path is kept only as a backward-compatible alias). Some tools work without an API key under rate limits; most require a Jina API key for full access. Server-side tool filtering via URL query parameters (include_tools/exclude_tools/include_tags/exclude_tags/max_tokens) lets clients register only the tools they need to save context tokens.

Tools

primer
Get current contextual information (time, locale) for localized, time-aware responses; no API key required
read_url
Extract clean, structured content from web pages as markdown via the Reader API; API key optional
capture_screenshot_url
Capture high-quality screenshots of web pages via the Reader API; API key optional
guess_datetime_url
Analyze a web page for its last-update/publish datetime with confidence scores; no API key required
search_web
Search the entire web for current information and news via the Reader API; API key required
search_web_deep
Search the web, read each result page via the Reader API, then score every passage against the query in one listwise Reranker API call (jina-reranker-v3.5) to return the best passage per page; API key required
search_arxiv
Search academic papers and preprints on arXiv via the Reader API; API key required
search_ssrn
Search academic papers on SSRN (Social Science Research Network) via the Reader API; API key required
search_images
Search for images across the web, similar to Google Images, via the Reader API; API key required
search_jina_blog
Search Jina AI news and blog posts at jina.ai/news; no API key required
search_bibtex
Search for academic papers and return BibTeX citations (DBLP + Semantic Scholar); no API key required
expand_query
Expand and rewrite search queries using the query expansion model via the Reader API; API key required
parallel_read_url
Read multiple web pages in parallel for efficient content extraction via the Reader API; API key optional
parallel_search_web
Run multiple web searches in parallel for comprehensive topic coverage and diverse perspectives; API key required
parallel_search_arxiv
Run multiple arXiv searches in parallel for comprehensive research coverage; API key required
parallel_search_ssrn
Run multiple SSRN searches in parallel for comprehensive social science research coverage; API key required
sort_by_relevance
Rerank documents by relevance to a query via the Reranker API; API key required
classify_text
Classify texts into user-defined labels via the Embeddings API; API key required
deduplicate_strings
Get the top-k semantically unique strings via the Embeddings API and submodular optimization; API key required
deduplicate_images
Get the top-k semantically unique images via the Embeddings API and submodular optimization; API key required
extract_pdf
Extract figures, tables, and equations from PDF documents (arXiv papers or any PDF URL) using layout detection; API key required
show_api_key
Utility tool related to the configured API key (exact behavior depends on implementation)

Setup

1) If your client supports remote MCP servers natively (Cursor, LM Studio, Claude Code), add url: https://mcp.jina.ai/v1 with an optional Authorization: Bearer ${JINA_API_KEY} header. 2) If your client lacks remote MCP support (e.g. some Claude Desktop setups), connect through the local mcp-remote proxy via npx, passing the server URL and Authorization header as args. 3) For Claude Code, run claude mcp add -s user --transport http jina https://mcp.jina.ai/v1 --header "Authorization: Bearer ${JINA_API_KEY}". 4) For OpenAI Codex, edit ~/.codex/config.toml to add an mcp_servers entry that launches mcp-remote. 5) Optionally filter which tools get registered server-side via query params, e.g. ?exclude_tags=parallel or ?include_tags=search,read, to save context window space.

claude_desktop_config.json
{"mcpServers":{"jina-mcp-server":{"url":"https://mcp.jina.ai/v1","headers":{"Authorization":"Bearer ${JINA_API_KEY}"}}}}

Fit and risk

Best for

  • Developers who want to give an LLM real-time web search and reading capability
  • Researchers doing academic literature review across arXiv and SSRN
  • Teams needing semantic deduplication or classification of text/image sets
  • Users with a Jina API key who want one remote MCP server usable across multiple clients

Not for

  • Fully offline or air-gapped environments with no outbound network access
  • Users unwilling to obtain a Jina API key, since most tools require one for full access and unauthenticated use is rate-limited
  • Latency-sensitive workflows, since tools like search_web_deep can take 2-20 seconds per call

Required permissions

  • An optional or required Jina API key (Bearer token) for accessing the Reader/Embeddings/Reranker APIs and higher rate limits
  • Outbound network access from the server to target URLs, search engines, and Jina's cloud APIs

Risks and side effects

  • This is a hosted remote server at mcp.jina.ai — queries and fetched page content pass through Jina's cloud infrastructure
  • API keys stored in plaintext config files or environment variables can be exposed if configs are shared or leaked
  • Rate limits apply to tools used without an API key, which can bottleneck heavy usage
  • Some tools (e.g. search_web_deep) have noticeably longer response times, which can affect interactive workflows

Troubleshooting

  1. Stuck in a tool-calling loop: usually caused by a too-small local model context window (e.g. LM Studio's default 4096); increase the context length
  2. Not seeing all tools: some clients cache tool definitions locally — remove and re-add the server to force a refresh
  3. Claude Desktop shows 'Server disconnected' on Windows: a known mcp-remote arg-escaping bug with spaces; work around it by passing the Authorization header via an environment variable without spaces around the colon
  4. Cursor shows a red dot on MCP status: a known Cursor UI bug that doesn't affect functionality; toggle the MCP off/on to restart the local proxy
  5. Content getting truncated: Claude Code, Claude Desktop, and Cursor enforce a 25k token limit on MCP responses, so the server truncates read_url/parallel_read_url output by default; adjust with ?max_tokens= or disable with max_tokens=0
  6. Upgrading from /sse: if previously added with --transport sse, remove it first (claude mcp remove -s user jina) then re-add using --transport http

Use cases

Give an LLM assistant live web reading and clean markdown extraction from arbitrary URLs
Perform web, image, arXiv, and SSRN search directly from a conversation
Rerank, classify, or semantically deduplicate search results and candidate documents
Extract figures, tables, and equations from PDFs or arXiv papers
Run multiple searches or page reads in parallel for broader, faster research coverage

Supported clients

CursorFull support
LM StudioFull support
Claude CodeFull support
Claude DesktopPartial support
OpenAI CodexPartial support
WindsurfPartial support