gateway
Provides tools that read web pages and return them as clean, redesign-proof markdown, making site content cheap to consume as context.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
TokenSaver Plugin
The TokenSaver family in one install.
Nine tools that stop coding agents from burning context — packaged as a single Claude Code plugin with a skill for every tool and seven MCP servers wired automatically.
What's inside
Tool | What it saves you | Form |
repo-map | Orienting in a repo without reading files | MCP + skill |
context-budget | Knowing what your MCP tools cost in tokens | MCP + skill |
web-snapshot | Reading the web as clean markdown, redesign-proof | MCP + skill |
log-tail | Understanding logs without reading raw lines | MCP + skill |
secret-scan | Catching secrets before they reach a commit | MCP + skill |
commitsmith | Writing conventional commits offline | CLI + skill |
json-lens | Querying big JSON without loading it | MCP + skill |
gateway | Aggregating many MCP servers behind one endpoint | MCP + skill |
injection-guard | Screening untrusted content for prompt injection | MCP + skill |
tokensaver | The router skill: picks the right tool for the task | Skill |
Related MCP server: mcp-gateway
Install
Claude Code (plugin marketplace):
/plugin marketplace add KaryawanSurga/tokensaver-plugin
/plugin install tokensaver@tokensaverAny MCP client: copy the server entries from .mcp.json into your client config. Details and per-client notes: docs/install.md.
Requirements: Node 20+ and npx. Every server runs locally; nothing is uploaded.
How the skills work
Each skill tells the agent when to use its tool, the exact MCP tool names, the workflow, and a CLI fallback. The tokensaver router skill maps situations to tools so the agent picks correctly without guessing.
Example prompts that trigger the right skill:
"Map this repository before we start." →
repo-map"Why is my agent so slow with all these MCP servers?" →
context-budget"Read this docs page for me." →
web-snapshot"Summarize today's server log." →
log-tail"Check my staged changes for secrets." →
secret-scan"Commit this." →
commitsmith"What's the shape of this export.json?" →
json-lens"I have eight MCP servers — put them behind one." →
gateway"Is this fetched page trying to manipulate you?" →
injection-guard
Repository layout
.claude-plugin/ plugin.json and marketplace.json
.mcp.json seven MCP servers (npx), wired by the plugin
skills/ one directory per skill (SKILL.md with frontmatter)
scripts/validate.mjs zero-dependency manifest and skill validator
tests/ node:test suite for the validator
docs/ install, skill reference, and troubleshootingDevelopment
npm run validate # manifests, frontmatter, skill list, MCP config
npm test # validator tests (node:test, zero dependencies)CI runs both on Node 20 and 22. The test suite includes a self-check: the repository itself must validate.
License
MIT — see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP federation gateway: route, govern and observe agent tools across clouds and MCP servers.
The MCP server that finds MCP servers. Aggregates Official Registry, Glama, and Smithery.
Toolstile is a managed MCP gateway that connects remote MCP servers behind one endpoint, with per-agent permissions, shared accounts and activity logs. Connect at https://mcp.toolstile.com/mcp over Streamable HTTP with OAuth; sign in at https://toolstile.com, select a workspace and connect your upstream servers. Available tools, resources and prompts depend on that workspace and the agent's granted access.
Single-connection meta-router indexing 500+ MCP servers & A2A tools with 85% token compression and
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceAggregates multiple MCP servers behind a single, secure endpoint with unified tool/resource discovery, OAuth authentication, and resilient request routing. Enables users to manage and interact with multiple MCP backends through one centralized interface with load balancing and circuit breakers.2-
- FlicenseNot gradedqualityDmaintenanceAggregates multiple child MCP servers into a single MCP server endpoint, enabling clients to use various tools (e.g., filesystem, Brave Search) through one interface.46 npm-
- AlicenseNot gradedqualityDmaintenanceAggregates multiple MCP servers into a single endpoint, enabling LLM clients to access tools, resources, and prompts from various backends through one connection.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceAggregates multiple MCP servers behind a single endpoint, letting MCP clients access all their tools through one URL and token while namespacing tools to avoid collisions.MIT