Skip to main content
Glama
MCK564

token-context-mcp

by MCK564
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to token-context-mcp

No user-submitted related servers found.

    Related Servers

    • codeloupe-mcp

      ndhkaeru
      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

    • @centr-ai/mcp

      chiragpgauswami
      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

    • Sippion

      Sitten-Tokyo
      F
      license
      Not graded
      quality
      A
      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.
      -

    • repogrammar_context

      SioYooo
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP tool that provides local-first, source-backed repository context for coding agents, returning metadata and a bounded read plan without requiring full file reads.
      7 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 10 tools

    Disambiguation3/5

    Most tools target distinct phases (list repos, index status, search, orient, read context, traverse graph), but boundaries blur in places: get_symbol_context and inspect_symbol both return source packets plus edges for a symbol, and get_impact_slice, get_module_dependents, and search_source(expand='graph') all traverse relationships. Descriptions attempt to differentiate via 'one call', 'lexical vs semantic', and 'candidate vs complete', but an agent could still misselect among them.

    Naming Consistency5/5

    Every tool follows a consistent verb_noun snake_case pattern (get_*, find_*, list_*, search_*, inspect_*). Prefixes map cleanly to intent: get for retrieval, find/list/search for discovery. No mixed conventions.

    Tool Count5/5

    Ten tools is well-scoped for a code-context/index server. Each tool earns its place across discovery, search, orientation, symbol reading, and graph traversal, with no redundant filler.

    Completeness4/5

    Coverage spans repository listing, index freshness, symbol search, orientation maps, file skeletons, bounded source context, and impact traversal — a solid read-only surface with no obvious dead ends. Minor gaps like direct line-range/file-read or cross-repo comparison are workable around via existing tools.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources