Filesystem Context
Give agents read-only, bounded access to search and analyze your repo tree without accidental edits during review or audit passes.
Overview
Filesystem Context MCP is a MCP server for the Ship phase that provides read-only filesystem exploration, search, and analysis for safer agent reviews.
What is this MCP server?
- Read-only MCP server for filesystem exploration, search, and analysis
- npm package @j0hanz/filesystem-context-mcp (v1.0.9), stdio transport
- Safer than full read-write filesystem MCP when you only need inspection
- Supports structured codebase navigation for review and documentation tasks
- Complements write-capable filesystem MCP when agents need separate browse vs mutate roles
- Version 1.0.9, npm identifier @j0hanz/filesystem-context-mcp
- Transport type stdio
- Capability focus: read-only exploration, search, and analysis
Community signal: 8 GitHub stars.
What problem does it solve?
Full filesystem MCP access makes it easy for agents to modify files when you only wanted them to search or understand the codebase.
Who is it for?
Builders who want a dedicated browse-and-search MCP server alongside optional write tools for implementation tasks.
Skip if: Workflows that require the agent to create, rename, or delete project files through MCP in the same session.
What do I get? / Deliverables
After registration, agents can explore and analyze allowed directories read-only, lowering accidental write risk during review workflows.
- Read-only file and directory search results in agent sessions
- Safer review workflows without MCP-mediated writes
- Structured filesystem analysis under scoped roots
Recommended MCP Servers
Journey fit
Read-only exploration shines at Ship review and security-minded passes, while still supporting Build-time context gathering. Code review and pre-merge analysis are the canonical shelf where safe filesystem reads prevent destructive agent mistakes.
How it compares
Read-only MCP filesystem lens, not the mutable @j0hanz/filesystem-mcp or a git-only diff skill.
Common Questions / FAQ
Who is filesystem-context for?
Developers using MCP agents who need codebase search and analysis without granting write access to the local filesystem.
When should I use filesystem-context?
Use it during code review, architecture audits, or incident triage when the agent should read and search files but not modify them.
How do I add filesystem-context to my agent?
Install @j0hanz/filesystem-context-mcp, add it as a stdio MCP server in your client config, and scope allowed root paths per the package documentation.