Skip to main content
Glama
104,547 servers. Updated

Matching MCP tools:

Matching MCP Connectors:

"A tool for managing entire project code context" matching MCP servers:

GET /v1/servers – MCP directory API reference
  • A
    license
    Not graded
    quality
    F
    maintenance
    A local, provider-neutral MCP server for repository-scoped issue handling. It provides a guarded interface to Linear, GitHub Issues, GitHub Projects v2, and Jira Cloud, with preview/apply safety and host-local configuration.
    30 npm
    1
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    An MCP server that acts as a context-aware code retrieval broker for AI coding agents, enforcing backpressure and token budgeting to prevent context window overflow.
    4
    43 npm
    MIT
  • A
    license
    B
    quality
    C
    maintenance
    Enables LLMs to efficiently read, write, and refactor code using precise AST-based operations, reducing token usage and context window waste.
    25
    25 npm
    3
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    A persistent memory layer for Claude Code that maintains project information, technology stack, tasks, decisions, and session history between coding sessions, eliminating the need to re-explain project context.
    9
    MIT
  • F
    license
    Not graded
    quality
    A
    maintenance
    It reads a project's kickoff card, acceptance criteria, AGENTS rules, progress, Git trail, and handoff package, and appends validated, audited progress events tied to project-record Git commits. This gives Codex agents scoped, credential-bound access to resumable project context and safe handoffs.
    -
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables agents to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited progress events with matching Git commits through short-lived scoped credentials.
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to retrieve Git-backed project context, handoff packages, progress, and next steps, and to append validated progress events with matching project-record commits. This supports visible agent progress, resumable work, and safe handoffs while keeping high-risk actions outside the MCP surface.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Builds rich code graphs from TypeScript/NestJS codebases using AST analysis and Neo4j, enabling semantic search, natural language querying, and intelligent graph traversal to provide deep contextual understanding of code relationships and dependencies.
    41 npm
    17
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Indexes codebases into a SQLite database to provide metadata, exports, dependency graphs, and change tracking for JS/TS projects. It enables users to search for symbols, map internal dependencies, and monitor file changes through MCP tools and a web dashboard.
    1,185 npm
    5
    MIT
  • F
    license
    Not graded
    quality
    A
    maintenance
    Enables Codex agents to read a project's kickoff card, acceptance criteria, progress, Git trail, and handoff package, then append one validated, idempotent progress event with an agent verification note and matching Git commit. Access is limited to short-lived, scoped, revocable credentials bound to a single workspace and project, with high-risk actions kept outside the tool surface.
    -
  • F
    license
    Not graded
    quality
    A
    maintenance
    Enables MCP clients to read a project's Git-backed kickoff, acceptance criteria, handoff package, progress, and next step, and to append validated, audited progress events as project records. It provides short-lived scoped credentials and fail-closed tool allowlisting for safe, resumable AI-assisted development.
    -
  • F
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents and humans to read a project's kickoff card, acceptance criteria, handoff package, progress, Git trail, and next step, then append audited, idempotent progress events that are committed to the project's Git record. Access is scoped per project through short-lived, revocable credentials, keeping high-risk actions outside the tool surface for human approval.
    -