What is the base path and why is it required?
The base path is a mandatory directory that limits all file operations. It ensures security by confining scans, extractions, and copies to that directory only.
@cdgaete
Basic information
A tool to analyze directory structures while being mindful of token limitations for LLMs. Customize ignore files like gitignore patterns, such as .venv or node_modules
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"TokenScope": {
"command": "uv",
"args": [
"run",
"--with",
"tokenscope",
"tokenscope",
"--base-path",
"/your/secure/base/path"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
TokenScope is a Model Context Protocol (MCP) server that provides token-aware directory structure analysis and file content extraction for Large Language Models. It helps LLMs understand codebases efficiently by respecting token limits and filtering via .gitignore patterns.
Configure TokenScope with a mandatory base path for security, then invoke its six tools (e.g., scan_directory_structure, extract_file_content, search_files_by_pattern, analyze_token_usage, generate_directory_report, copy_file_to_destination) from any MCP-compatible client. All operations are confined to the allowed directory and automatically respect .gitignore rules.
The base path is a mandatory directory that limits all file operations. It ensures security by confining scans, extractions, and copies to that directory only.
The server estimates token counts and uses smart extraction to stay within configurable token limits, providing only as much content as the LLM can process.
Yes, it automatically filters out files and directories matched by .gitignore patterns in the scanned directory, reducing noise and saving tokens.
TokenScope is an MCP server; it requires a runtime environment with the MCP protocol and access to the filesystem it scans. No additional databases or external services are needed.
The `copy_file_to_destination` tool operates exclusively within the allowed base path, preventing any file operations outside that directory. Destination files must also reside inside the base path.
A Box model context protocol server to search, read and access files
Markdown To PDF Conversion MCP
The SSE version of the MCP service is modified from the Filesystem MCP server

AI tools (Claude, ChatGPT, Gemini, Grok, etc.) generate HTML constantly, from reports to landing pages to prototypes, but there's no easy way to share it or know if anyone looked. HTMLvault turns any HTML into a clean, t
filesystem MCP server for accessing WSL distributions from Windows
Comments