Schema | TokenLens MCP Server

TokenLens MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`TOKENLENS_DATA_DIR`	No	Path to a custom data directory containing pricing JSON files.
`TOKENLENS_DATA_URL`	No	URL to fetch live pricing data from. Defaults to bundled local files if not set. Falls back to bundled data if unreachable.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
compare_plansA	Rank all TokenLens plans by effective cost per 1M tokens. Useful when choosing between subscriptions and API access for a given model.
run_scenarioA	Calculate total monthly token usage and cost (API vs subscription) for a given usage pattern. Returns costs for all matching plans side-by-side.
break_evenA	Find the daily usage hours at which API cost equals a subscription price. Below this threshold, the API is cheaper; above it, the subscription wins.
recommend_planA	Get a single best-value plan recommendation for your usage profile. Considers whether a subscription or API access is cheaper, and whether token caps are sufficient.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/flikQ/tokenlens-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server