"Understanding the Concept of LLM Context" matching MCP servers:

MCP server providing virtual memory for AI context with durable SQLite storage, retrieval, and bounded prompt assembly to manage context windows.

Enables coding agents to publish HTML pages and small sites over MCP, returning a stable link and keeping every version, with access limited to specific people, an organization, or anyone with the link.

An MCP server that keeps raw tool output out of the context window by sandboxing and compressing results (about 98% reduction), persisting file edits, git operations, tasks and decisions in SQLite with BM25 retrieval so the agent resumes after compaction, and enforcing routing across 17 platforms via MCP and hooks. It also encourages the model to write scripts that compute answers and log only results instead of reading large data into context.

Blind multi-model councils with anonymous LLM seats and direct 1:1 chat as a local MCP server. Enables asking one question to get independent answers from multiple model CLIs, then blind scoring and reveal.

Plan your projects with The High Council! Several AI models from different labs argue about your idea, then debate on Software Engineering choices. The goal is to get everyone to work together, in harmony and with manners. Effectiveness is unproven, but it is a fun way to spend your tokens!

Enables a primary agent to offload bounded, high-volume analysis of explicitly selected workspace files to an auxiliary LLM through a single read-only tool, returning text, Markdown, JSON, or unified-diff output with token usage while retaining all planning, verification, and edits.

Enables agents and users to route prompts to the cheapest reachable free or paid model across providers, compare costs, list filtered models, and receive fallback chains and cached routing results without calling any LLM API.

MCP server that provides a live coordination layer for AI agents, including attributable handoffs, a shared event ledger, atomic work-claiming, and advisory file leases to prevent collisions.

Enables AI agents to interact with multiple LLM providers (OpenAI, Anthropic, Google, DeepSeek) through a standardized interface, making it easy to switch between models or use multiple models in the same application.

MCP server for the LLM Wiki Chrome extension that exposes bounded browser automation tools (shared tabs, accessibility snapshots, screenshots, clicks, typing, etc.) with explicit user consent and strict typing, enabling local agents to interact with specific web pages via a native messaging relay.

A small MCP server that lets Claude (or any MCP client) ask other models what they think.

Wraps Tool and ToolPackage instances from the llm-chat ecosystem behind the Model Context Protocol, enabling stdio and Streamable HTTP transports for MCP servers.

MCP proxy that reduces context usage through semantic tool routing, enabling on-demand discovery and routing of relevant tools.

Provides MCP tools to profile and optimize LLM conversation context, identifying token waste and applying deterministic fixes to reduce context window usage.

Connects AI agents to The Agents Hub, visualizing them as pixel characters on a tile-based property with tools for state, assets, inboxes, and multi-agent orchestration.

Enables cost-aware LLM routing over MCP with verification-based cascading, offering tools for routing queries, resuming escalated approvals, estimating costs, comparing policies, and explaining routing decisions, plus read-only resources and a policy-selection prompt.

Enables Claude to offload noisy commands, large files, and web research to a local OpenAI-compatible LLM, receiving only concise cited answers instead of the raw material. It also optionally delegates writing a single file inside an isolated git worktree, retrying until a Claude-authored test passes.

A meta-server that aggregates multiple MCP servers into a single interface, reducing token usage by 98%+ through progressive tool discovery and direct code execution that processes data between tools without consuming context window space.

A local-first LLM routing MCP server that keeps sensitive data on your own models, with fail-closed privacy and manager-worker delegation, exposing route and complete tools to any MCP client.

Enables delegating mechanical or high-volume subtasks to a local LLM through an MCP tool, letting the assistant query the local model without using its own output tokens for content.