Jina AI MCP
Jina AI Remote MCP Server
Jina AI's official remote MCP server: pages to Markdown, web search, arXiv, reranking and embeddings
Install
claude mcp add -s user --transport http jina https://mcp.jina.ai/v1 \
--header "Authorization: Bearer ${JINA_API_KEY}"This is third-party code. Review the repository files before installing.
What it does
The server gives an agent tools built on Jina AI's Reader, Embeddings and Reranker APIs. It turns web pages into clean Markdown, captures screenshots, guesses publish dates, searches the web, images, arXiv and SSRN, returns BibTeX for papers and extracts tables and equations from PDFs. It has parallel search and read variants, document reranking, text classification and semantic deduplication. Tools can be filtered with URL parameters so unused descriptions do not take up model context.
Who it is for. For researchers, analysts and developers who need their agent to read and search the web.
Good fit when
- You need to read several pages as clean text
- You need fresh web results or arXiv papers
- You need to rank found documents by relevance
Not a fit when
- Data must not leave for an external service
- You need locally hosted search
Example request
Find recent arXiv papers on reranking, read the top three and summarize themLimitations
Search, reranking and embeddings need a Jina API key; page reading works without one but with rate limits. The server is remote and all requests go to Jina AI. Claude Code, Claude Desktop and Cursor cap tool responses, so long pages are truncated with a note.
How to disable. In Claude Code run claude mcp remove -s user jina; in other clients delete the jina-mcp-server block from the MCP config.
MCP
- Transport
- http
- Authentication
- API key
| Environment variables | |
|---|---|
| JINA_API_KEY secret | Jina API key sent in the Authorization header; required for search, reranking and embeddings |
Security check
- Sends queries and page URLs to the external Jina AI service
- Uses a secret API key
README in short
The README has a tool table noting which tools need a key. It gives configs for clients with remote server support, mcp-remote for the rest, and commands for Claude Code and Codex. It covers tool filtering via URL parameters and tag groups. Troubleshooting explains truncation of long responses, client-side tool caching and Windows issues.
FAQ
Does it work without a key?
Partly: page reading, screenshots and BibTeX search work without a key but are rate limited. Search needs a key.
How do I reduce the number of tools?
Add include_tags, exclude_tags, include_tools or exclude_tools to the endpoint URL.
Related
CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP
A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief
The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces
A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills