Skip to main content
Glama
@lex-tools/codebase-context-dumper

@lex-tools/codebase-context-dumper

Official
by lex-tools

codebase-context-dumper MCP Server

npm version License: Apache-2.0

A Model Context Protocol (MCP) server designed to easily dump your codebase context into Large Language Models (LLMs).

Why Use This?

Large context windows in LLMs are powerful, but manually selecting and formatting files from a large codebase is tedious. This tool automates the process by:

  • Recursively scanning your project directory.

  • Including text files from the specified directory tree that are not excluded by .gitignore rules.

  • Automatically skipping binary files.

  • Concatenating the content with clear file path markers.

  • Supporting chunking to handle codebases larger than the LLM's context window.

  • Integrating seamlessly with MCP-compatible clients.

Related MCP server: code-index-mcp

The easiest way to use this tool is via npx, which runs the latest version without needing a local installation.

Configure your MCP client (e.g., Claude Desktop, VS Code extensions) to use the following command:

{
  "mcpServers": {
    "codebase-context-dumper": {
      "command": "npx",
      "args": [
        "-y",
        "@lex-tools/codebase-context-dumper"
      ]
    }
  }
}

The MCP client will then be able to invoke the dump_codebase_context tool provided by this server.

Features & Tool Details

Tool: dump_codebase_context

Recursively reads text files from a specified directory, respecting .gitignore rules and skipping binary files. Concatenates content with file path headers/footers. Supports chunking the output for large codebases.

Functionality:

  • Scans the directory provided in base_path.

  • Respects .gitignore files at all levels (including nested ones and .git by default).

  • Detects and skips binary files.

  • Reads the content of each valid text file.

  • Prepends a header (--- START: relative/path/to/file ---) and appends a footer (--- END: relative/path/to/file ---) to each file's content.

  • Concatenates all processed file contents into a single string.

Input Parameters:

  • base_path (string, required): The absolute path to the project directory to scan.

  • num_chunks (integer, optional, default: 1): The total number of chunks to divide the output into. Must be >= 1.

  • chunk_index (integer, optional, default: 1): The 1-based index of the chunk to return. Requires num_chunks > 1 and chunk_index <= num_chunks.

Output: Returns the concatenated (and potentially chunked) text content.

Local Installation & Usage (Advanced)

If you prefer to run a local version (e.g., for development):

  1. Clone the repository:

    git clone git@github.com:lex-tools/codebase-context-dumper.git
    cd codebase-context-dumper
  2. Install dependencies:

    npm install
  3. Build the server:

    npm run build
  4. Configure your MCP client to point to the local build output:

    {
      "mcpServers": {
        "codebase-context-dumper": {
          "command": "/path/to/your/local/codebase-context-dumper/build/index.js" // Adjust path
        }
      }
    }

Contributing

Contributions are welcome! Please see CONTRIBUTING.md for details on development, debugging, and releasing new versions.

License

This project is licensed under the Apache License 2.0. See the LICENSE file for details.

Available Tools

1 tool
dump_codebase_contextA

Recursively reads text files from a specified directory, respecting .gitignore rules and skipping binary files. Concatenates content with file path headers/footers. Supports chunking the output for large codebases.

Inputs: base_path (required), num_chunks, chunk_index.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clearly defined purpose.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or conventions.

    Tool Count2/5

    One tool is too few for most practical server purposes, as it severely limits functionality and interaction. While the tool is well-described, a single tool feels thin and incomplete for a codebase context server.

    Completeness2/5

    The server's purpose appears to be codebase context management, but with only a dump tool, there are significant gaps. Missing operations like search, filter, update, or delete context make the surface incomplete and likely insufficient for agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers