MCP.so
ログイン

Python File Manager MCP Server

@anthropics

基本情報

カテゴリ

その他

トランスポート

stdio

作者

anthropics

投稿者

idoubi

Python File Manager MCP Server について

A Python MCP server for file operations

Python File Manager MCP Server の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

Python File Manager MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Python File Manager MCP?

Python File Manager MCP is a Python-based MCP server that provides file management capabilities such as file operations and directory management. It is designed for Claude Desktop users (≥0.10.0) and demonstrates proper MCP protocol implementation in a Desktop Extension.

How to use Python File Manager MCP?

Configure the server in an MCP client using the entry point server/main.py with the required arguments --workspace=${user_config.workspace_directory}. Ensure Python 3.8 or later (but <4) is installed. The server exposes three tools: list_files, read_file, and get_file_info.

Key features of Python File Manager MCP

  • List files in a directory
  • Read file contents
  • Get detailed file information
  • Configurable workspace directory
  • Debug mode output support

Use cases of Python File Manager MCP

  • Browsing and inspecting files in a designated workspace
  • Reading configuration or log files through an MCP client
  • Obtaining metadata (size, dates, etc.) for files
  • Learning Python-based MCP server development

よくある質問

1

What tools does Python File Manager MCP provide?

It provides three tools: `list_files` (list files in a directory), `read_file` (read file contents), and `get_file_info` (get information about a file).

2

What are the runtime requirements?

Python version 3.8 or later but less than 4. The server is compatible with macOS, Windows, and Linux.

3

How do I set the workspace directory?

Set the `workspace_directory` in the user configuration; the default is `${HOME}/Documents`. It can be changed to any accessible directory.

4

Does it require authentication?

The README does not mention any authentication mechanism. The server likely operates within the local filesystem scope as configured.

5

What transport does it use?

The README does not specify a transport; it implements the MCP protocol, which typically uses stdio or other transports as defined by the MCP client.

コメント

「その他」の他のコンテンツ