Skip to main content
Glama
MCP JinaAI Reader Server

MCP JinaAI Reader Server

by spences10

mcp-jinaai-reader


⚠️ Notice

This repository is no longer maintained.

The functionality of this tool is now available in mcp-omnisearch, which combines multiple MCP tools in one unified package.

Please use mcp-omnisearch instead.


A Model Context Protocol (MCP) server for integrating Jina.ai's Reader API with LLMs. This server provides efficient and comprehensive web content extraction capabilities, optimized for documentation and web content analysis.

Related MCP server: Jina AI Remote MCP Server

Features

  • 📚 Advanced web content extraction through Jina.ai Reader API

  • 🚀 Fast and efficient content retrieval

  • 📄 Complete text extraction with preserved structure

  • 🔄 Clean format optimized for LLMs

  • 🌐 Support for various content types including documentation

  • 🏗️ Built on the Model Context Protocol

Configuration

This server requires configuration through your MCP client. Here are examples for different environments:

Cline Configuration

Add this to your Cline MCP settings:

{
	"mcpServers": {
		"jinaai-reader": {
			"command": "node",
			"args": ["-y", "mcp-jinaai-reader"],
			"env": {
				"JINAAI_API_KEY": "your-jinaai-api-key"
			}
		}
	}
}

Claude Desktop with WSL Configuration

For WSL environments, add this to your Claude Desktop configuration:

{
	"mcpServers": {
		"jinaai-reader": {
			"command": "wsl.exe",
			"args": [
				"bash",
				"-c",
				"JINAAI_API_KEY=your-jinaai-api-key npx mcp-jinaai-reader"
			]
		}
	}
}

Environment Variables

The server requires the following environment variable:

  • JINAAI_API_KEY: Your Jina.ai API key (required)

API

The server implements a single MCP tool with configurable parameters:

read_url

Convert any URL to LLM-friendly text using Jina.ai Reader.

Parameters:

  • url (string, required): URL to process

  • no_cache (boolean, optional): Bypass cache for fresh results. Defaults to false

  • format (string, optional): Response format ("json" or "stream"). Defaults to "json"

  • timeout (number, optional): Maximum time in seconds to wait for webpage load

  • target_selector (string, optional): CSS selector to focus on specific elements

  • wait_for_selector (string, optional): CSS selector to wait for specific elements

  • remove_selector (string, optional): CSS selector to exclude specific elements

  • with_links_summary (boolean, optional): Gather all links at the end of response

  • with_images_summary (boolean, optional): Gather all images at the end of response

  • with_generated_alt (boolean, optional): Add alt text to images lacking captions

  • with_iframe (boolean, optional): Include iframe content in response

Development

Setup

  1. Clone the repository

  2. Install dependencies:

npm install
  1. Build the project:

npm run build
  1. Run in development mode:

npm run dev

Publishing

  1. Update version in package.json

  2. Build the project:

npm run build
  1. Publish to npm:

npm publish

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT License - see the LICENSE file for details.

Acknowledgments

Available Tools

1 tool
read_urlB

Convert any URL to LLM-friendly text using Jina.ai Reader

Inputs: url (required), no_cache, format, timeout, +7 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'read_url' follows a clear verb_noun pattern.

    Tool Count2/5

    One tool is too few for a server with a purpose that could reasonably support more operations, such as handling different URL types or providing metadata extraction. This minimal set feels thin and under-scoped for the domain.

    Completeness2/5

    The server's domain appears to be URL content reading, but the single tool only covers basic text conversion. There are obvious gaps, such as no tools for handling errors, extracting structured data, or managing different content formats, which limits agent effectiveness.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      F
      maintenance
      Integrates Jina.ai's Grounding API with LLMs for real-time, fact-based web content grounding and analysis, enhancing LLM responses with precise, verified information.
      1
      20 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides access to Jina AI's web reading, search, embeddings, and reranking capabilities. Enables URL content extraction, web/arXiv/image search, document deduplication, and relevance ranking through natural language.
      Apache 2.0
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides web content extraction, search capabilities (web, arXiv, SSRN, images), semantic deduplication, and reranking through Jina AI's Reader, Embeddings, and Reranker APIs.
      1
      Apache 2.0