{"id":"qiangmzsx-mcp-filesystem-server","name":"mcp-filesystem-server","homepage":null,"repo_url":"https://github.com/qiangmzsx/mcp-filesystem-server","category":"devtools","subcategories":[],"tags":["mcp","filesystem","local-integration","go"],"what_it_does":"mcp-filesystem-server is a Go implementation of an MCP (Model Context Protocol) server that exposes filesystem access to an MCP-capable client (e.g., Claude Desktop) with a configured allowlist of directories.","use_cases":["Letting an LLM safely read files from specific local directories via MCP","Building local toolchains where the model can browse code/docs on disk","Prototyping MCP integrations for filesystem-backed workflows"],"not_for":["Handling sensitive production data without additional hardening","Exposing unrestricted filesystem access or multi-user shared hosts","Use as an API service over the network without verifying MCP transport and sandboxing"],"best_when":"You run the server locally (or in a tightly controlled environment) and explicitly pass the directories you want the model to access.","avoid_when":"You cannot restrict the accessible paths, cannot audit the server’s filesystem operations, or plan to run it in an untrusted/multi-tenant environment.","alternatives":["Other MCP filesystem servers (e.g., mark3labs/mark3labs-based implementations)","Custom MCP server wrapping a restricted file reader","Instead of MCP, use a dedicated local file service with explicit allowlists and auditing (then expose as MCP tool)"],"af_score":38.8,"security_score":33.0,"reliability_score":21.2,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:37:23.081611+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Implicit/local-process usage (no auth mentioned in README)"],"oauth":false,"scopes":false,"notes":"README does not describe authentication/authorization beyond the directory allowlist passed as command arguments."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; appears to be a self-hosted open-source tool."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":38.8,"security_score":33.0,"reliability_score":21.2,"mcp_server_quality":45.0,"documentation_accuracy":35.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":90.0,"rate_limit_clarity":0.0,"tls_enforcement":0.0,"auth_strength":20.0,"scope_granularity":60.0,"dependency_hygiene":40.0,"secret_handling":50.0,"security_notes":"Security posture is largely unknown from the README. The main apparent control is a directory allowlist passed as command-line args. There is no mention of authentication, encryption/TLS, audit logging, sandboxing, or operational limits (file size, recursion depth). Since it targets filesystem access, least-privilege and OS-level containment are important.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":30.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Filesystem allowlist is configured via args; agent may still attempt broader paths unless the server enforces strict allowlisting","Running locally in an editor/desktop integration may inherit host filesystem permissions (ensure OS-level sandboxing if needed)","No guidance is provided in the README about limits (max file size, directory depth) or performance/error behavior"]}}