jina-ai/MCP
If you are the rightful owner of MCP and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
The Jina AI Remote MCP Server provides access to various APIs for extracting, searching, and processing web content, images, and academic papers.
Jina AI Remote MCP Server
A remote Model Context Protocol (MCP) server that provides access to Jina Reader, Embeddings and Reranker APIs with a suite of URL-to-markdown, web search, image search, and embeddings/reranker tools:
Tool | Description | Is Jina API Key Required? |
---|---|---|
primer | Get current contextual information for localized, time-aware responses | No |
read_url | Extract clean, structured content from web pages as markdown via Reader API | Optional* |
capture_screenshot_url | Capture high-quality screenshots of web pages via Reader API | Optional* |
guess_datetime_url | Analyze web pages for last update/publish datetime with confidence scores | No |
search_web | Search the entire web for current information and news via Reader API | Yes |
search_arxiv | Search academic papers and preprints on arXiv repository via Reader API | Yes |
search_images | Search for images across the web (similar to Google Images) via Reader API | Yes |
expand_query | Expand and rewrite search queries based on the query expansion model via Reader API | Yes |
parallel_search_web | Run multiple web searches in parallel for comprehensive topic coverage and diverse perspectives via Reader API | Yes |
parallel_search_arxiv | Run multiple arXiv searches in parallel for comprehensive research coverage and diverse academic angles via Reader API | Yes |
sort_by_relevance | Rerank documents by relevance to a query via Reranker API | Yes |
deduplicate_strings | Get top-k semantically unique strings via Embeddings API and submodular optimization | Yes |
deduplicate_images | Get top-k semantically unique images via Embeddings API and submodular optimization | Yes |
Optional tools work without an API key but have rate limits. For higher rate limits and better performance, use a Jina API key. You can get a free Jina API key from https://jina.ai
Usage
For client that supports remote MCP server:
{
"mcpServers": {
"jina-mcp-server": {
"url": "https://mcp.jina.ai/sse",
"headers": {
"Authorization": "Bearer ${JINA_API_KEY}" // optional
}
}
}
}
For client that does not support remote MCP server yet, you need mcp-remote
a local proxy to connect to the remote MCP server.
{
"mcpServers": {
"jina-mcp-server": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.jina.ai/sse"
// optional bearer token
"--header",
"Authorization: Bearer ${JINA_API_KEY}"
]
}
}
}
Troubleshooting
I got stuck in a tool calling loop - what happened?
This is a common issue with LMStudio when the default context window is 4096 and you're using a thinking model like gpt-oss-120b
or qwen3-4b-thinking
. As the thinking and tool calling continue, once you hit the context window limit, the AI starts losing track of the beginning of the task. That's how it gets trapped in this rolling context window.
The solution is to load the model with enough context length to contain the full tool calling chain and thought process.
I can't see all tools.
Some MCP clients have local caching and do not actively update tool definitions. If you're not seeing all the available tools or if tools seem outdated, you may need to remove and re-add the jina-mcp-server to your MCP client configuration. This will force the client to refresh its cached tool definitions. In LMStudio, you can click the refresh button to load new tools.
Developer Guide
Local Development
# Clone the repository
git clone https://github.com/jina-ai/MCP.git
cd MCP
# Install dependencies
npm install
# Start development server
npm run start
Deploy to Cloudflare Workers
This will deploy your MCP server to a URL like: jina-mcp-server.<your-account>.workers.dev/sse