Skip to main content
Glama
token-context-mcp

token-context-mcp

Related Servers

Alternatives to token-context-mcp

  • A
    license
    B
    quality
    F
    maintenance
    A Model Context Protocol (MCP) server that provides code analysis capabilities using tree-sitter, designed to give Claude intelligent access to codebases with appropriate context management.
    26
    625 PyPI
    312
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    A fully featured coding agent that uses symbolic operations (enabled by language servers) and works well even in large code bases. Essentially a free to use alternative to Cursor and Windsurf Agents, Cline, Roo Code and others.
    29
    31,250 PyPI
    31,560
    GPL 3.0
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI assistants to search and analyze codebases using Abstract Syntax Tree (AST) pattern matching with ast-grep. Supports structural code search, pattern testing, and AST visualization across multiple programming languages.
    4
    500
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables coding agents to inspect files, search text, compare directories, read symbols, and apply structured edits against large codebases through bounded, local-first MCP tools.
    4
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI coding agents to retrieve token-budgeted project context, search code symbols, look up definitions, and access project memory and cross-project learnings through local MCP tools. It reduces redundant exploration by supplying the smallest useful context from a deterministic, local-first index.
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables AI coding agents to retrieve focused, bounded repository context locally and read-only, reducing token usage while never modifying the repository or executing its code.
    -
  • A
    license
    A
    quality
    B
    maintenance
    Local, read-only MCP server for coding agents. Indexes repeated implementations in your repository (FastAPI routes, pytest fixtures, Pydantic and SQLAlchemy models) and returns source-backed examples with a bounded read plan, or a typed UNKNOWN when evidence is insufficient. No LLM or network calls.
    1
    13 npm
    MIT

TDQS

A4.2/5.0

Scored across 10 tools

Disambiguation4/5

Each tool has a documented niche and the descriptions actively redirect the agent (e.g. get_module_dependents says use get_impact_slice for symbol edges, find_symbols says use search_source for code text), which resolves most overlap. The residual ambiguity is between name-based lookups (find_symbols vs inspect_symbol) and between get_symbol_context vs get_impact_slice, where the boundary is 'bulk vs single' and 'body+edges vs edges only' — learnable but easy to misselect on a first pass.

Naming Consistency5/5

All ten tools follow a strict snake_case verb_noun pattern (list_repositories, get_repo_map, find_symbols, inspect_symbol, search_source). The verb choice is also semantically meaningful — get for retrieval, find for pattern matching, search for full-text, inspect for a one-shot packet — rather than arbitrary variation.

Tool Count5/5

Ten tools is squarely in the well-scoped range for a code-context/indexing server. Each tool covers a distinct retrieval granularity (repo, file, module graph, symbol, source text) and none feels like filler.

Completeness4/5

The read-only surface is broad: repo discovery, freshness checking, ranked maps, name matching, file skeletons, symbol bodies, call edges, import graphs, and full-text search — a full navigation lifecycle for the stated purpose. Gaps are minor (no cross-repo search, no way to retrieve a whole file body, budget profiles are only listable, not configurable), but agents can work around them by composing tools.

Maintenance

ActivityActive
ResponsivenessNo recent community issues