Skip to main content
Glama
enesjakozh
owayo

MCP Source Tree Server

by owayo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

MCP Source Tree Server

指定されたディレクトリ配下のファイルツリーを生成するMCPサーバーです。 .で始まるディレクトリや.gitignore に記載された条件に従って、特定のファイルやディレクトリを除外します。 Claudeに組み込むことで、Claudeがプロジェクトの構造を素早く確認でき、Claudeが編集すべきファイルを特定するのに役立ちます。

機能

  • 指定されたディレクトリ配下のファイルツリーをJSON形式で取得

  • .gitignore の条件に従ってファイル/ディレクトリを除外

  • ディレクトリ構造を階層的なJSONで表現

Related MCP server: EliteMCP

セットアップ

必要条件

  • Python 3.10以上

  • uv

インストール

# uvのインストール
$ curl -LsSf https://astral.sh/uv/install.sh | sh

$ cd /path/to/mcp-src-tree
# ライブラリのインストール
$ uv sync

Claude for Desktopでの設定

claude_desktop_config.json に以下の設定を追加してください：

{
    "mcpServers": {
        "src-tree": {
            "command": "uv",
            "args": [
                "--directory",
                "/path/to/mcp-src-tree",  # このプロジェクトディレクトリの絶対パスに書き換えてください
                "run",
                "tree.py"
            ]
        }
    }
}

Claudeでの使用例

指示するのはsrcの一つ上のルートディレクトリを指定してください。 .gitignore を考慮する場合、ルートディレクトリ直下に .gitignore が存在することが前提です。 /Users/xxx/GitHub/xxx/ のソースツリーを確認してください のように指示すると動作します

以下のように応答します

はい、ソースツリーを確認させていただきます。
プロジェクトの構造を確認しました。以下のような構成になっています：
src/
└── xxxx/
    ├── __init__.py
    ├── converter.py
    ├── html_converter.py
    ├── image_processor.py
    ├── toc_analyzer.py
    └── utils.py

これにより、Claudeが素早くプロジェクトの構造を確認できます。

ファイル除外

.で始まるディレクトリは自動的に除外されます。 .gitignore に記載されているパターンに合致するファイルやディレクトリは、ツリーから自動的に除外されます。 例えば、以下のような .gitignore の設定が有効です：

__pycache__/
node_modules/
*.log

Available Tools

1 tool
get_src_treeC

Generate a file tree for the specified directory, filtering files based on .gitignore. Traverses the filesystem and generates a JSON-formatted tree structure that preserves hierarchy.

ParametersJSON Schema
NameRequiredDescriptionDefault
directoryYes

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It discloses that the tool traverses filesystems, generates JSON output, and applies .gitignore filtering. However, it omits critical behavioral details like error handling, performance characteristics (e.g., recursion depth, large directory handling), authentication needs, or rate limits. For a filesystem tool with zero annotation coverage, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately concise with three sentences that directly address functionality. It's front-loaded with the core purpose and avoids unnecessary elaboration. However, the second sentence could be more tightly integrated with the first for better flow, slightly affecting structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of filesystem traversal and JSON generation, with no annotations and no output schema, the description is incomplete. It mentions the output format ('JSON-formatted tree structure') but doesn't describe the structure's schema, error cases, or edge behaviors (e.g., symbolic links, permissions). For a tool with rich potential outputs and zero structured documentation, this falls short.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, with one parameter ('directory') undocumented in the schema. The description adds context by specifying it's for 'the specified directory' and mentions .gitignore filtering, which implies the directory should be a valid path. However, it doesn't explain parameter format (e.g., absolute vs. relative paths) or constraints, leaving gaps in parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Generate a file tree for the specified directory, filtering files based on .gitignore.' It specifies the verb ('generate'), resource ('file tree'), and key behavior (gitignore filtering). However, with no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives. It mentions the core functionality but lacks context about prerequisites, limitations, or comparison to other file operations. With no sibling tools, this gap is less critical but still represents a lack of usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool update
    • First observedget_src_tree
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'get_src_tree' follows a clear verb_noun pattern.

Tool Count2/5

A single tool is too few for most practical server purposes, as it severely limits functionality and flexibility. This server appears to offer only basic directory tree generation, which feels thin and under-scoped.

Completeness2/5

The server's domain seems to be file system or source tree operations, but with only one tool for generating a tree, there are significant gaps. Missing operations might include filtering by other criteria, updating trees, or handling file contents, making the surface incomplete for typical agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches