Provides tools that read web pages and return them as clean, redesign-proof markdown, making site content cheap to consume as context.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@gateway I have six MCP servers — put them all behind one endpoint"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
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
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.
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
.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 troubleshootingnpm 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.
MIT — see LICENSE.
This server cannot be deployed
The MCP server that finds MCP servers. Aggregates Official Registry, Glama, and Smithery.
Stateless MCP gateway and OTel span-streaming bridge for hosted MCP servers.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Trust, freshness, policy, and discovery layer for public MCP servers.
