mcp-server and MCP

These are ecosystem siblings—Glean provides enterprise search/knowledge management API integration while Jina offers web scraping and retrieval capabilities, both serving as specialized data source connectors within the MCP server ecosystem rather than competing for the same use case.

mcp-server
65
Established
MCP
50
Established
Maintenance 13/25
Adoption 15/25
Maturity 18/25
Community 19/25
Maintenance 13/25
Adoption 10/25
Maturity 9/25
Community 18/25
Stars: 55
Forks: 20
Downloads: 1,263
Commits (30d): 0
Language: TypeScript
License: MIT
Stars: 533
Forks: 59
Downloads:
Commits (30d): 3
Language: TypeScript
License: Apache-2.0
No risk flags
No Package No Dependents

About mcp-server

gleanwork/mcp-server

MCP server for Glean API integration

Implements a monorepo architecture with separate packages for server runtime and client configuration, deployable via npx or Docker. Provides tooling to configure the MCP server with popular MCP clients through the `@gleanwork/configure-mcp-server` package. Enables local execution of Glean API queries through the Model Context Protocol, connecting AI applications directly to Glean's enterprise search capabilities.

About MCP

jina-ai/MCP

Official Jina AI Remote MCP Server

Exposes 19 tools for web search, content extraction, academic research, and semantic operations via Jina's Reader, Embeddings, and Reranker APIs. Uses Streamable HTTP transport for remote MCP compatibility with Claude, LM Studio, and other clients, with optional stdio proxy support for older integrations. Includes server-side tool filtering via query parameters to reduce context window overhead by selectively registering only needed capabilities.

Scores updated daily from GitHub, PyPI, and npm data. How scores work