MCP server for JinaAI search
MCP server for JinaAI search. Exposed over MCP by the mcp jinaai search mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
The functionality of this tool is now available in mcp-omnisearch, which combines multiple MCP tools in one unified package.
Everything the assistant can do here goes through one of these:
search — Search the web and get clean, LLM-friendly content using Jina.ai Reader. Returns top 5 results with URLs and clean contentSetup — The Setup tool exposed by this serverPublishing — The Publishing tool exposed by this servermcp-jinaai-search on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: JINAAI_API_KEY. 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.
Plenty of search and retrieval servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Jinaai Search's toolset — search, Setup, Publishing — is a fair guide to whether it matches your workflow. It is maintained by spences10; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| search | Search the web and get clean, LLM-friendly content using Jina.ai Reader. Returns top 5 results with URLs and clean content. |
| Setup | The Setup tool exposed by this server. |
| Publishing | The Publishing tool exposed by this server. |
{
"mcpServers": {
"jinaai-search": {
"command": "node",
"args": ["-y", "mcp-jinaai-search"],
"env": {
"JINAAI_API_KEY": "your-jinaai-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| JINAAI_API_KEY | Credential the server authenticates with. | Yes |
The simplest web tool that matters — fetch any URL and get model-ready markdown back.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Put 6,000+ pre-built scrapers at your assistant's fingertips through one MCP endpoint.