Token-Optimized MCP Server
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., "@Token-Optimized MCP Server Fetch and distill the content at https://example.com"
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.
Token-Optimized MCP Server
A high-performance Model Context Protocol (MCP) server built with Node.js and TypeScript. This server is purpose-built to minimize LLM token consumption through YAML serialization, structural HTML-to-Markdown distillation, and pre-flight token counting via the BPE tokenizer.
Table of Contents
Related MCP server: readdown-mcp
Overview
Modern AI agents connected via MCP suffer from context window exhaustion when tool responses contain verbose JSON payloads or raw HTML. This server addresses the problem at the architecture layer:
Optimization Strategy | Token Reduction |
YAML serialization over JSON | ~40–48% |
HTML → structured Markdown | ~60–80% |
Pre-flight token gating | Prevents overflow |
All diagnostic logging is routed to stderr to preserve the JSON-RPC protocol integrity on stdout.
Available Tools
extract_web_content
Fetches a web page, strips HTML noise, and returns clean, semantically structured Markdown optimized for LLM consumption.
Parameter | Type | Required | Description |
|
| Yes | A valid URL to fetch and convert. |
Example input:
{
"url": "https://example.com"
}Returns: Token-efficient Markdown with preserved heading hierarchy, links, and tables. Token count is logged to stderr.
query_metrics_database
Queries an internal metrics database and returns the results serialized in YAML format to reduce token overhead by approximately 45% compared to equivalent JSON.
Parameter | Type | Required | Description |
|
| Yes | A natural-language or structured query string. |
Example input:
{
"query": "Show CPU and memory usage for the last hour"
}Returns: YAML-formatted metrics payload. If the response exceeds 8,000 tokens, a warning is emitted to stderr recommending semantic chunking.
Note: The metrics database initializes automatically as an in-memory instance on server startup. No external setup, schema migration, or configuration is required.
Prerequisites
Node.js v18.0.0 or higher
npm v9+ (bundled with Node.js 18+)
Verify your installation:
node --version # Must be >= 18.0.0
npm --versionInstallation
# Clone or navigate to the project directory
cd optimized-mcp-server
# Install all dependencies
npm installDependencies at a Glance
Package | Purpose |
| Official MCP server SDK |
| Runtime input schema validation |
| BPE token counting (OpenAI compatible) |
| High-fidelity HTML → Markdown conversion |
| Native Rust-binding Markdown converter |
| JSON → YAML serialization |
Building
Compile the TypeScript source to JavaScript:
npm run buildThe compiled output is written to the build/ directory.
Configuration
To connect this server to an MCP-compatible AI host, register it in the host's configuration file. Below are copy-pasteable templates for common hosts.
Claude Desktop
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"token-optimized-server": {
"command": "node",
"args": [
"/absolute/path/to/optimized-mcp-server/build/index.js"
]
}
}
}Important: Replace
/absolute/path/to/with the actual absolute path on your system. On Windows, use double backslashes (\\) or forward slashes (/) in JSON strings.
After saving, fully quit and restart Claude Desktop to re-initialize the JSON-RPC handshake.
VS Code / Antigravity IDE
Add the following to your MCP configuration file (typically mcp_config.json in your editor's settings directory):
{
"mcpServers": {
"token-optimized-server": {
"command": "node",
"args": [
"/absolute/path/to/optimized-mcp-server/build/index.js"
]
}
}
}Windows example:
"args": [ "C:\\Users\\YourName\\projects\\optimized-mcp-server\\build\\index.js" ]
Usage
Development Mode
Run the server directly from TypeScript source using tsx (no build step required):
npm run devProduction Mode
Build first, then start the compiled server:
npm run build
npm startMCP Inspector
The MCP Inspector provides a browser-based UI for testing tools, simulating LLM requests, and inspecting JSON-RPC messages — no API keys required.
npx @modelcontextprotocol/inspector node build/index.jsThis launches a local proxy and opens the Inspector UI in your default browser. Use it to:
Verify the protocol handshake completes successfully.
Execute
extract_web_contentwith a test URL.Execute
query_metrics_databaseand confirm YAML output.Monitor
stderrlogs for token counts and threshold warnings.
Project Structure
optimized-mcp-server/
├── src/
│ └── index.ts # Core server implementation
├── build/ # Compiled JavaScript output (generated)
├── node_modules/ # Dependencies (generated)
├── package.json # Project metadata and scripts
├── tsconfig.json # TypeScript compiler configuration
├── .gitignore # Git exclusion rules
├── README.md # This fileLicense
ISC
Available Tools
2 toolsextract_web_contentA
Fetches raw HTML and converts it into structurally sound, token-efficient Markdown. Preserves semantic tags for AI readability.
Inputs: url (required).
query_metrics_databaseC
Queries internal metrics. Outputs strictly in YAML format for maximum token efficiency.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have entirely distinct domains: one handles web content extraction, the other queries a metrics database. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern using snake_case, making them predictable and disambiguated.
With only 2 tools, the server feels thin for its name 'Token-Optimized MCP Server' which implies a broader scope. The count is borderline acceptable.
The server name suggests a focus on token optimization, but the tools only cover web extraction and database queries. Key operations like text optimization or token analysis are missing.
Maintenance
Related MCP Connectors
Web pages and PDFs to clean, LLM-ready Markdown with token counts, small crawls and RAG chunks.
Free no-LLM token savers: URL→Markdown, outline, JSON trim, log compress, token count; x402 extras
Any web page as clean, LLM-ready Markdown with metadata, outline and token counts. Free preview.
YouTube transcripts, TikTok videos, Instagram profiles, Reddit threads & HN MCP (-87% LLM tokens).
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceFetches web pages and converts them to clean, readable markdown format by extracting main content while removing navigation, ads, and other non-essential elements to minimize token usage.4-
- AlicenseAqualityDmaintenanceConverts web pages and HTML strings into clean, LLM-optimized Markdown with metadata extraction and token estimation. It uses a lightweight, browserless approach to provide token-efficient output for more effective LLM processing.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables token-efficient web page fetching by converting HTML to Markdown with tiered access (outline, section, search) to minimize LLM context usage.Apache 2.0
- FlicenseAqualityDmaintenanceReduces token consumption by 73-87% by cleaning web and API data before it reaches the LLM context window. Supports fetching URLs, searching the web, optimizing JSON, and more.61-