tokenizer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | No | Anthropic API key for token counting via the messages.count_tokens endpoint. If not set, Claude token counting falls back to tiktoken's o200k_base encoding. | |
| ANTHROPIC_TOKEN_COUNT_MODEL | No | The default Claude model to use when the caller omits the model argument in token counting tools. | claude-opus-4-8 |
Instructions
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.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| count_tokensA | Count tokens in text. |
| count_tokens_fileA | Count tokens in a UTF-8 file. |
| count_tokens_folderA | Count tokens across all text files in a folder, recursively. |
| count_lines_fileA | Count lines in a file (str.splitlines semantics: a trailing newline adds no empty line). |
| count_chars_fileA | Count characters (Unicode code points) in a UTF-8 file. |
| count_kb_fileA | File size in KB as ceil(bytes / 1024), matching Windows Explorer. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct input (text, file, folder) or metric (tokens, lines, chars, KB), so there is no overlap. The count_tokens variants are clearly separated by scope.
All tools follow the predictable count_<metric>_<target> pattern, with count_tokens as the base form. Naming is uniform and easy to infer.
Six tools is well-scoped for a tokenizer server: three for token counting across input types and three for basic file size/line/character metrics. Every tool earns its place.
The surface covers token counting for text, files, and folders, plus file-level character, line, and byte-size metrics. No obvious gaps exist for the stated purpose.