RAG-Anything vs tldr MCP Gateway

RAG-Anything is an all-in-one Retrieval-Augmented Generation framework from HKUST's Data Systems Group that handles multimodal documents through a single unified pipeline. Unlike RAG frameworks that only handle plain text, it natively ingests and retrieves across text, tables, images, scientific figures, and mixed-modality documents without requiring separate preprocessing pipelines for each type. The framework covers the full RAG stack: document parsing, chunking strategies adapted to content type, embedding, vector storage, retrieval ranking, and generation. It's built to handle the kinds of documents that real enterprise workloads throw at you — PDFs with embedded tables, research papers with figures, reports that mix structured and unstructured content. With 16,000+ stars and academic backing from HKUDS (the same group behind LightRAG), it carries credibility beyond typical weekend projects. The key insight is that most RAG failures in production happen at the parsing and modality-handling stage, not the retrieval stage. By making multimodal handling a first-class concern rather than a bolt-on, RAG-Anything aims to close the gap between RAG demos and RAG production deployments.

tldr is a local proxy that sits between your AI coding harness and upstream MCP servers, solving one of the most underappreciated problems in agentic workflows: context bloat from tool schema proliferation. When you connect GitHub MCP, filesystem MCP, and a few others, you can easily be sending 24,000+ tokens of tool schemas to the model before any work begins. Instead of passing all those schemas directly, tldr exposes exactly five wrapper tools to the model: search_tools, execute_plan, call_raw, inspect_tool, and get_result. The model learns which underlying tools exist on-demand through search_tools, then calls them through the proxy. GitHub MCP's 24,473-token schema surface compresses to 3,482 tokens — an 86% reduction. Output responses are further compressed through field stripping, a 4,096-token cap, and a 64KB byte limit. This is a genuinely practical solution for power users running multi-MCP setups who've noticed degraded performance as their tool count grows. The tradeoff is one extra hop of indirection, but the token savings pay for themselves in improved model attention and lower API costs.