Jina MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Binding address | 0.0.0.0 |
| MCP_PORT | No | HTTP port for the MCP server | 8000 |
| MCP_AUTH_TOKEN | No | Bearer token for authentication (optional) | |
| MCP_ALLOWED_HOSTS | No | Reverse proxy Host whitelist (optional) |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_readerC | Fetch clean webpage content via Jina Reader |
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
With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clear.
The naming is descriptive and follows a common pattern (verb_noun). As a single tool, consistency is not an issue.
Only one tool is provided, which is too few for a server named 'Jina MCP Server'. The server likely expects more tools (e.g., search, summarize) to justify its name and purpose.
The server only covers webpage reading, missing other expected functionalities such as searching or processing content. This is a significant gap relative to the server's implied scope.