Practical overview
When it fits
Use it when an MCP-compatible client needs access to Jina’s search, reading, PDF extraction, embedding or reranking tools within an existing assistant workflow.
Who it is for
- People configuring MCP-compatible assistants or clients to use Jina tools.
- Developers building MCP-based research and retrieval workflows.
Documented uses
- Search the web, academic sources, images or Jina’s blog from an MCP client.
- Read webpages and PDFs as Markdown, capture webpage screenshots, or extract PDF figures, tables and equations.
- Rerank documents against a query or create semantically diverse strings using Jina’s APIs.
- Restrict the tools registered with a client to selected tools or categories.
Requirements & limits
The README marks some tools as requiring a Jina API key and others as optional-key or key-free. It states that optional tools are subject to rate limits without a key and that a key provides higher limits.
- A client with remote MCP support can use the server endpoint directly; the README documents
mcp-remoteas a local proxy option for clients without that support. - Some tools require a Jina API key, while the documented optional-key tools have rate limits without one.
- Endpoint filters can reduce which tool definitions the client registers; the README notes that registered tool schemas use context even when not called.
- The repository identifies TypeScript as the implementation language and Apache-2.0 as its license.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Connect a client that supports remote MCP
Add the Jina remote MCP server endpoint to an MCP-compatible client.
Before you start
- An MCP client that supports remote MCP servers.
- A Jina API key for tools that require one; the authorization header is optional for the direct remote-server configuration.
Steps
Add a server entry named
jina-mcp-serverto the client configuration.Set its URL to
https://mcp.jina.ai/v1.Add an
Authorizationheader withBearer ${JINA_API_KEY}when using a key; if the client does not support environment variables, replace the variable with the actual key.
Expected outcome
The client is configured to connect to Jina’s remote MCP server and expose its available tools.
Guide limitations
- Some tools require a Jina API key; optional-key tools are subject to rate limits without one.
- Some clients do not expand environment variables in configuration.
Limit registered tools with endpoint filters
Configure the server URL to expose a selected tool group or exclude specified tools before client registration.
Before you start
- An MCP client configured to connect to the Jina remote server.
- The server endpoint URL
https://mcp.jina.ai/v1.
Steps
Choose an
include_tags,exclude_tags,include_toolsorexclude_toolsquery parameter.Add the parameter to the endpoint URL; for example, use
?include_tags=search,readto select those tool groups.Save the filtered URL in the client’s server configuration.
Expected outcome
The endpoint filters the tools presented for registration, helping limit the tool definitions added to the client context.
Guide limitations
- The documented filter precedence is
exclude_tools,exclude_tags,include_tools, theninclude_tags. - The guide documents configuration, not verification of the resulting client tool list.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 12 October 2026
- Original website title
- jina-ai/MCP · Official homepage title · retained in its source language

