Flux MCP
OfficialRelated Servers
Alternatives to Flux MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read public web content as clean Markdown, search a private library of previously read documents, and access these tools via MCP, REST API, CLI, and WebMCP.23MIT
- AlicenseAqualityCmaintenanceEnables any MCP-compatible AI coding client such as Claude Code, Codex, or Cursor to run web searches and fetch pages as Markdown through a self-built search engine, with per-day and per-month spend caps, prompt-injection fencing on retrieved content, and local usage/cost reporting. Search results can be filtered by site, language, and date, and repeated page fetches within a short window are not billed twice.31MIT
- AlicenseBqualityBmaintenanceEnables AI coding assistants to perform real-time web searches for technical documentation and deep-fetch web pages, returning clean structured results. It supports integration with MCP clients such as Cursor, Claude, and CodeBuddy.3108 npm1MIT
- AlicenseAqualityCmaintenanceGives MCP-capable agents live web access: search the web, scrape pages into Markdown (including JavaScript-heavy and bot-protected sites), and extract named fields as JSON, with job polling, token-aware content offloading, and built-in research guidance. Ships as a self-hostable stdio or HTTP service with spend caps and per-request key support.7MIT
- AlicenseAqualityBmaintenanceEnables MCP-compatible AI agents to search, scrape, crawl, map, and interact with live web pages, returning clean, structured, agent-ready content. It also supports recurring page monitoring, autonomous deep research, and credit-usage checks.261MIT
- AlicenseAqualityBmaintenanceEnables AI agents to search the web with clean page text, crawl websites into Markdown, extract articles and structured data, and monitor Google News and press releases for LLM context and RAG pipelines. It works with MCP clients and uses the user's own Apify API token for pay-per-result data retrieval.6MIT
TDQS
Scored across 4 tools
The tools have mostly distinct purposes: account checks billing, search finds sources, fetch returns a full page, and lineage extracts targeted passages. The main overlap is between fetch, lineage, and search because all can return web content, but the descriptions explicitly clarify when to use each.
All names are single lowercase words, which gives a consistent surface style. However, the set mixes nouns (account, lineage) with verbs (fetch, search), so it is readable but not a strict verb_noun convention.
Four tools is well-scoped for this server: billing, search, full-page retrieval, and grounded extraction. Each tool has a clear role and earns its place without bloat.
The core workflow is covered: check balance, search the web, fetch a page, and extract answers from a document or URL. Minor gaps exist around batch reading or managing multiple sources, but agents can work around them by making repeated calls.