Skip to main content
Glama

Related Servers

Alternatives to tokenizer-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for estimating LLM token consumption and costs from project documents, code, and materials. Provides 8 tools including project budget planning, token/cost estimation, GitHub repo analysis, and pricing refresh.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that helps AI agents reduce token usage by converting data to TOON format and stripping comments and unnecessary whitespace from code files.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous agents to tokenize session context windows and compact dialogue history deterministically, exposing this capability to MCP-compatible clients like Claude Desktop and Cursor. Helps manage context length and reduce token usage in agent sessions through a zero-dependency Python MCP server.
      7
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides file and directory tools for LLMs, including project structure analysis, file reading, and project context resources, with support for .gitignore patterns.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Token-efficient MCP server for multi-language project analysis (Java, TypeScript, JavaScript, Markdown, Python) with plugins, semantic search, and static analysis.
      MIT

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All tools follow the predictable count_<metric>_<target> pattern, with count_tokens as the base form. Naming is uniform and easy to infer.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues