Jina AI MCP Tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| port | No | HTTP server port (only for HTTP transport) | 3000 |
| transport | No | Transport type: stdio or http | stdio |
| JINA_API_KEY | No | Jina AI API Key (Optional) - Get a free API key from https://jina.ai/?sui=apikey for enhanced features. Required for search functionality. | |
| search-endpoint | No | Search endpoint to use: standard (s.jina.ai) or vip (svip.jina.ai) | standard |
| tokens-per-page | No | Tokens per page for pagination | 15000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jina_readerC | Read and extract content from web page. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusion or misselection. Its purpose is clearly distinct.
With a single tool named jina_reader, consistency is trivially satisfied. It follows a readable snake_case pattern.
A server branded as 'Jina AI MCP Tools' with only one tool seems too few for the apparent scope. Jina AI typically offers multiple capabilities (search, embeddings, reranking), so one tool feels under-provisioned.
The surface only covers web page reading, with no search, embedding, reranking, or other operations implied by the Jina AI brand. This is a severely incomplete toolset for the stated purpose.