MCP Compact
Related Servers
Alternatives to MCP Compact
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceConsolidates multiple upstream MCP servers behind a single STDIO interface, exposing search_tools and run_tool to avoid context bloat.380 npm20MIT- AlicenseNot gradedqualityCmaintenanceAggregates multiple downstream stdio MCP servers behind a single endpoint, namespacing their tools so AI clients can discover and call filesystem, GitHub, SQLite, and other tools through one connection. Provides crash detection, auto-restart, configurable timeouts, and structured logging for resilient operation.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAggregates multiple MCP servers behind a single stdio interface, supporting stdio-based and HTTP SSE-based upstreams with OAuth.4 npmMIT
- AlicenseNot gradedqualityDmaintenanceAggregates multiple upstream MCP servers (stdio, streamable-http, sse, websocket) behind a single streamable-HTTP endpoint with declarative configuration, namespacing, filtering, and auto-reload.MIT
- AlicenseNot gradedqualityCmaintenanceStarts local MCP backend servers only when their tools are called, exposes their tools through a single stdio gateway, preserves stateful sessions, and can stop safely restartable backends after idle timeouts.1MIT
- AlicenseNot gradedqualityCmaintenanceAggregates multiple MCP servers behind a single endpoint, exposing their tools as one flattened prefixed list and routing each call back to the correct backend, with shared processes, lazy start, and hot config reload. Supports per-agent server scopes and an on-demand mode that collapses a large toolset into a search-and-call pair.MIT
TDQS
Scored across 2 tools
The two tools are clearly separated by purpose: invoke handles tool calls and read handles resource access. The descriptions provide explicit examples and modes to guide usage, though the generic proxy nature could occasionally blur the line between a tool and a resource.
Both tool names are single-word verbs in a consistent imperative style, making them predictable and easy to remember. There is no mixing of conventions or misleading synonyms.
With only two tools, the set is intentionally minimal but well-suited for a compact projection surface that forwards to a larger MCP ecosystem. While it feels thin compared to direct-integration servers, its purpose justifies the small count.
The server covers the core interaction patterns (invoking tools and reading resources) and includes validation/preview modes. However, it lacks an explicit discovery mechanism to list available servers, tools, or resource templates, which could be a significant gap for agents without prior knowledge.