Jina Reader & Search MCP 远程 MCP 服务器 – 官方端点、工具列表与一键连接指南
Jina AI 官方远程 MCP 服务器。AI 代理可将 URL 读取为干净文本、搜索网页与图片、对文档重排序并生成嵌入(Bearer Key;tools/list 支持匿名握手)。
本页收录其官方远程端点、传输协议、认证方式、全部工具 Schema、实时可用性拨测与安全审计结果,并为 Cursor、Claude Code、VS Code、ChatGPT 等 10 大客户端提供一键接入指引。
🔒 Client-side only — never leaves your browser.
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"jina": {
"url": "https://mcp.jina.ai/v1",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}claude mcp add --transport http jina https://mcp.jina.ai/v1
With credential header:
claude mcp add --transport http jina https://mcp.jina.ai/v1 --header "Authorization: Bearer YOUR_API_KEY"
Or add to .vscode/mcp.json:
{
"servers": {
"jina": {
"type": "http",
"url": "https://mcp.jina.ai/v1",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}- Open Settings → Connectors (Integrations) → Add Custom Connector.
- Paste the endpoint URL:
https://mcp.jina.ai/v1 - Provide your API key / Bearer token when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"jina": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.jina.ai/v1",
"--header",
"Authorization: Bearer YOUR_API_KEY"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"jina": {
"serverUrl": "https://mcp.jina.ai/v1",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"jina": {
"url": "https://mcp.jina.ai/v1",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add to ~/.codex/config.toml — Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.jina] url = "https://mcp.jina.ai/v1" bearer_token_env_var = "JINA_TOKEN"
Add to cline_mcp_settings.json (Cline → MCP Servers → Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"jina": {
"type": "streamableHttp",
"url": "https://mcp.jina.ai/v1",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add to ~/.gemini/settings.json under mcpServers — httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"jina": {
"httpUrl": "https://mcp.jina.ai/v1",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}🧰 Jina Reader & Search MCP 工具与 Schema(6)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| read_url ~68 tok | 🟢 Read | Convert a URL to clean, LLM-ready markdown text. | url*: stringwithImages: boolean |
| search_web ~64 tok | 🟢 Read | Search the web via Jina's grounding API. | query*: stringnum: number |
| search_images ~50 tok | 🟢 Read | Search images relevant to a query. | query*: string |
| rerank_documents ~88 tok | 🟢 Read | Rerank a list of documents against a query. | query*: stringdocuments*: arraytopN: number |
| segment_text ~53 tok | 🟢 Read | Segment long text into semantic chunks. | content*: string |
| get_embeddings ~60 tok | 🟢 Read | Generate embeddings for texts with jina-embeddings. | texts*: array |
🛡️ 安全评级、质量与上下文 Token 审计
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- Static credential (Bearer token / API key) — protect it in client config
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
🔐 OAuth 2.1 与安全
- 认证方式
- Bearer Token
- 动态客户端注册(DCR)
- —
- PKCE S256
- —
- 受保护资源元数据
- https://mcp.jina.ai/.well-known/oauth-protected-resource
📡 官方远程端点与传输协议
远程端点 https://mcp.jina.ai/v1 采用 Streamable HTTP(流式 HTTP,2025-03-26 规范)。Streamable HTTP 在单一 POST 端点上完成 JSON-RPC 双向交互,是当前 MCP 规范推荐的传输方式,可直接被 Claude、Cursor、VS Code 等客户端以 URL 形式接入,无需 npx mcp-remote 桥接。
接入前可将端点粘贴至本站 在线 MCP Inspector 实测 initialize / tools/list 握手,确认真实协议行为。
🔐 认证与权限机制
认证方式为 Bearer Token。需要在客户端配置中提供 Authorization: Bearer <你的密钥> 请求头,凭据可在 Jina AI 控制台获取。
🛡️ 上下文开销与安全审计
该服务端当前登记 6 个工具,全部定义合计约 403 tokens,会在每次请求时注入模型系统提示词。安全评级为 A+,官方直营来源。工具名与 Schema 越精简,对上下文窗口的"税"越低;可用 feecalculator.app 估算每次调用的边际成本。
🧩 主流客户端快速接入
本站为 Jina Reader & Search MCP 生成了 Cursor / Claude Code / VS Code / ChatGPT / Windsurf / Kiro / Codex / Cline / Gemini 等 10 大客户端的专属配置——包括一键 deeplink、claude mcp add 命令与 JSON/TOML 片段。下方选择你的客户端即可查看 1 分钟接入步骤。代表性工具包括 read_url、search_web、search_images、rerank_documents、segment_text 等。
📖 Jina Reader & Search 详解
Jina Reader & Search MCP — Remote MCP Server
Jina's remote MCP aggregates its retrieval stack behind one Bearer token: read_url converts any page to LLM-clean markdown, search_web/images run s.jina.ai queries, and rerank/embeddings feed RAG pipelines — anonymous tools/list lets you audit the surface first.
Official Jina Reader & Search MCP Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.jina.ai/v1 - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Jina Reader & Search MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Jina Reader & Search MCP uses bearer-token authentication. Create an access token in your Jina AI account settings, then send it as Authorization: Bearer <token>. No OAuth redirect flow is involved.
All 6 cataloged tools are read-only — Jina Reader & Search MCP cannot mutate your account data, which makes it safe to connect broadly.
Common Troubleshooting & Connection Tips
- 401/403 responses — your credential is missing or rejected. Regenerate the key/token and make sure it is sent as an
Authorization: Bearerheader on every request, including theinitializecall. - "Session expired" / stale
Mcp-Session-Id— just re-sendinitialize; stateless clients can ignore session headers entirely. - A free Jina API key covers the reader tier; heavier search/embed usage is metered.
- read_url without a key works but is rate-limited — always send the Bearer header.
🚀 如何接入 Jina Reader & Search MCP 远程 MCP
- 获取远程端点 — 复制官方端点 https://mcp.jina.ai/v1,并先在 Jina AI 控制台申请 API 凭据。
- 写入客户端配置 — 在 Cursor 的 mcp.json / Claude Code CLI / 其他客户端中添加该 URL 与 Authorization 头(见下方分客户端指南)。
- 授权并验证 — 保存配置后,在本站 Inspector 中运行 initialize 与 tools/list 验证连通性。
🔌 Jina Reader & Search × 各客户端连接指南
❓ 常见问题
Jina Reader & Search MCP 远程 MCP 服务器是官方提供的吗?
本条目标记为「官方直营」。端点由 Jina AI 官方运营,所有收录端点均经过真实 MCP initialize 握手验证。
如何在 Claude / Cursor 中连接 Jina Reader & Search MCP?
复制远程端点 https://mcp.jina.ai/v1:Claude Code 执行 claude mcp add --transport http jina https://mcp.jina.ai/v1;Cursor 可直接使用本页的一键 deeplink 或在 ~/.cursor/mcp.json 中添加 { "mcpServers": { "jina": { "url": "https://mcp.jina.ai/v1" } } }。
连接时返回 401 或需要密钥怎么办?
该端点需要 Bearer Token / API Key:在 Jina AI 控制台申请凭据后,按对应客户端文档将其写入 headers 配置。
本地 stdio MCP 和这个远程 MCP 有什么区别?
本地 MCP 通过 npx/uvx 在你的机器上启动 stdio 子进程,依赖本地运行时且密钥以明文写入配置文件;远程 MCP 是 Jina AI 托管的 HTTPS 端点,免安装、支持 OAuth 2.1 授权流,且同一端点可跨桌面与移动端复用。详见 本地 vs 远程 MCP 对比。