Fetch with OHarness
- Connector
- Local servers
Fetch a URL and convert it to markdown for reading. OHarness works with Fetch out of the box.
What you get
| MCP connector | Runs locally as uvx mcp-server-fetch. |
| Published by | Model Context Protocol |
How it signs in
It does not. The server starts on your machine when a session needs it, through uv (install it once from docs.astral.sh/uv). There is no account to create and no key to set.
Try it
Once Fetch is connected, a first prompt to see it work:
Use the Fetch 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 Fetch under Connectors.
- Pick it. The server starts and its tools are available from the next turn.
Links
Common questions
Does OHarness work with Fetch?
Yes. Fetch ships in OHarness as an MCP connector, so it is in the menu on first launch with nothing to look up.
How does the Fetch connector sign in?
It does not need to. It runs as a process on your machine (uvx), with nothing to sign in to.
Is OHarness affiliated with Model Context Protocol?
No. OHarness works with Fetch through its public MCP server; Fetch and its logo belong to Model Context Protocol.
More in local servers
Everything · Filesystem · Git · Memory · Sequential thinking · Time
Fetch and its logo belong to Model Context Protocol. Listed because OHarness works with it, not because Model Context Protocol endorses OHarness.
Use Fetch from OHarness
The same Fetch tools in every session, whichever of the model providers is underneath.