Making remote MCP servers handle local files and generated artifacts
Remote MCP file bridge with sessions and artifact capture, but niche until MCP adoption broadens.
Local-first MCP gateway. One port for every tool and every AI client: lazy discovery (~90% token savings), tool integrity + quarantine, secrets in the OS keychain.
Slashes MCP token overhead by 96% using lazy discovery instead of dumping full tool catalogs.
Developers building or using AI agents with multiple MCP servers
Smithery · Gloo · MCP Inspector
Instead of exposing the full catalog, Toolport gives agents four small meta-tools and searches for the real tools on demand. With 62 tools, that reduced definition overhead from about 24k tokens to 900. In benchmarked tasks, total token use fell by up to 91% at the same success rate.
It is MIT licensed with Windows, macOS, and Linux installers. The same Rust gateway also runs headlessly through stdio, Streamable HTTP, OpenAPI, or Docker.
Remote MCP file bridge with sessions and artifact capture, but niche until MCP adoption broadens.
Single-file + live-reload is the practical win here: point your agents at one static URL and you can swap or share upstream MCP servers on the fly via TOML edits or the REST API. The per-tool fnmatch allow-lists, owner registration, and JWT/static token options show the author thought about multi-tenant workflows, but this is a focused infra tool — great when you actually run many MCP servers, less interesting otherwise.
Unified MCP runtime across Claude, Cursor, and Grok with cross-harness delegation.
Secret redaction and MCP tool integration for Cursor and similar AI clients.
The project maps the entire OAuth/MCP discovery-to-DCR funnel and gives actionable failure points — e.g., missing WWW-Authenticate headers, malformed PRM or issuer metadata, or broken token endpoints. It’s a focused, practical CLI that also fits into CI (GitHub Actions badge, quickscan command), so teams can catch auth regressions before rollout. Niche but very useful if you run or validate MCP/OAuth endpoints; wider adoption will depend on more examples and integration templates.
Uses your real Chrome session so agents bypass MFA instead of spinning up headless browsers.