Jina AI Model Context Protocol (MCP) server that integrates with Jina AI APIs for web reading and search
Jina AI Model Context Protocol (MCP) server that integrates with Jina AI APIs for web reading and search. The jina mcp tools mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.
It gives Codex, Claude Code, and other coding agents the two web capabilities they usually need while programming:
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Everything the assistant can do here goes through one of these:
Prerequisites — Set the API key in your shell if you want both search and reading:jina_reader — The default cache holds 50 URLs, and each page is limited to approximately 15,000 tokens. Both values are configurableYou will need 6 environment variables: JINA_API_KEY, NODE_USE_ENV_PROXY, HTTP_PROXY, HTTPS_PROXY, NO_PROXY, JINA_MCP_HTTP_AUTH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Jina MCP Tools's toolset — Prerequisites, jina_reader — is a fair guide to whether it matches your workflow. It is maintained by PsychArch; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Jina MCP Tools's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | Set the API key in your shell if you want both search and reading: |
| jina_reader | The default cache holds 50 URLs, and each page is limited to approximately 15,000 tokens. Both values are configurable. |
{
"mcpServers": {
"jina-mcp-tools": {
"command": "npx",
"args": ["-y", "jina-mcp-tools"],
"env": {
"JINA_API_KEY": "your-value",
"NODE_USE_ENV_PROXY": "your-value",
"HTTP_PROXY": "your-value",
"HTTPS_PROXY": "your-value",
"NO_PROXY": "your-value",
"JINA_MCP_HTTP_AUTH_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| JINA_API_KEY | Credential the server authenticates with. | Yes |
| NODE_USE_ENV_PROXY | Configuration value read at startup. | Optional |
| HTTP_PROXY | Configuration value read at startup. | Optional |
| HTTPS_PROXY | Configuration value read at startup. | Optional |
| NO_PROXY | Configuration value read at startup. | Optional |
| JINA_MCP_HTTP_AUTH_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.