mcp-server-qdrantofficial
A
licenseB
qualityD
maintenanceThis repository is an example of how to create a MCP server for Qdrant, a vector search engine.
2
1,552
Apache 2.0
bigapi
by BiGapi-2026
Related Servers
Alternatives to bigapi
- FlicenseAqualityAmaintenanceNode.js server implementing Model Context Protocol (MCP) for filesystem operations.414439,826 npm91,511-
Chroma MCP Serverofficial
AlicenseAqualityDmaintenanceA server that provides data retrieval capabilities powered by Chroma embedding database, enabling AI models to create collections over generated data and user inputs, and retrieve that data using vector search, full text search, and metadata filtering.1373,970 PyPI600Apache 2.0
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to capture any public URL as PNG, JPEG, or PDF via REST API or MCP tools, including screenshot capture, page description, and PDF rendering.11 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to render any URL or raw HTML into PDF files or PNG/JPEG/WebP screenshots over MCP stdio or Streamable HTTP. Output stays in memory with SSRF protection, bounded concurrency, and configurable size and timeout limits.8 npm1MIT
@rendershot/mcp-serverofficial
AlicenseAqualityDmaintenanceEnables AI agents to capture screenshots and generate PDFs from URLs or HTML via the Rendershot API.412 npm3MIT- AlicenseAqualityAmaintenanceEnables AI agents to scrape web pages into Markdown, text, HTML, JSON, PDFs, screenshots, and structured data, while managing batch scraping jobs, persistent browser sessions, usage/request history, and docs lookup through native MCP tools.25243 npmApache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to render website screenshots and PDFs, check page changes, and retrieve usage stats via REST calls.-
- AlicenseNot gradedqualityCmaintenanceEnables agents to scrape, crawl, map, search, and extract web pages as clean markdown or structured JSON directly through MCP tools.AGPL 3.0
TDQS
A4.9/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a distinct lifecycle role: discovery (find_tool), execution (run_operation), session convenience (enable_tools), key creation (get_access), and balance checking (get_balance). The descriptions explicitly cross-reference each other and state what they do not do, so there is little risk of an agent picking the wrong one.
Naming Consistency5/5
All five names follow a consistent snake_case verb_noun pattern (find_tool, run_operation, enable_tools, get_access, get_balance). The verbs are specific and match the action, and no style mixing or vague generic names appear.
Tool Count5/5
Five tools is well-scoped for a server that intentionally stays lean and dynamically exposes operations through find_tool/run_operation. Each tool covers a necessary concern: discovery, execution, optional tool enabling, access, and balance.
Completeness5/5
The core workflow is fully covered: obtain a key, find an operation, run it, and check credit/usage. The dynamic design means new operations don't require new server tools, so there are no obvious dead ends or missing lifecycle steps.
Maintenance
ActivityMaintained
ResponsivenessNo issues