Filesystem with OHarness
- Konektor
- Serwery lokalne
Read, write and search files under one directory — the project, unless you change it. OHarness works with Filesystem out of the box.
Ta strona jest napisana po angielsku. Terminy, które wyjaśnia, są tymi, których szuka się po angielsku, a przetłumaczony termin fachowy to już inny termin.
What you get
| MCP connector | Runs locally as npx -y @modelcontextprotocol/server-filesystem ${project}. |
| Published by | Model Context Protocol |
How it signs in
It does not. The server starts on your machine when a session needs it, through npx, which runs on the Node that OHarness already has. There is no account to create and no key to set.
Try it
Once Filesystem is connected, a first prompt to see it work:
Use the Filesystem server to help with this project, and show me each call you make.
Adding it
- Download OHarness for the Mac, or install the CLI anywhere Node runs.
- In the composer, open the + menu and find Filesystem under Connectors.
- Pick it. The server starts and its tools are available from the next turn.
Links
Common questions
Does OHarness work with Filesystem?
Yes. Filesystem ships in OHarness as an MCP connector, so it is in the menu on first launch with nothing to look up.
How does the Filesystem connector sign in?
It does not need to. It runs as a process on your machine (npx), with nothing to sign in to.
Is OHarness affiliated with Model Context Protocol?
No. OHarness works with Filesystem through its public MCP server; Filesystem and its logo belong to Model Context Protocol.
More in local servers
Everything · Fetch · Git · Memory · Sequential thinking · Time
Filesystem and its logo belong to Model Context Protocol. Listed because OHarness works with it, not because Model Context Protocol endorses OHarness.
Use Filesystem from OHarness
The same Filesystem tools in every session, whichever of the model providers is underneath.