Two fetch tools that differ only in destination is a deliberate split: read a page when you need to reason over it, write it to disk when you only need it kept. The Markdown and cleaning modes cut the same page down further. The third tool is a plain HTTP client, which is what makes this usable against APIs rather than only against pages.
An HTTP server with three tools: fetch a URL and read it back as Markdown or cleaned HTML, fetch the same URL straight to a file so it never enters the conversation, and issue an arbitrary request with your own method, headers and body.
- A page returned as Markdown, as raw HTML with the response headers, or cleaned to a level you choose
- The same fetch written to a file instead of the reply, for pages too large to read into context
- Any HTTP method — GET, POST, PUT, PATCH and DELETE — with query parameters, custom headers, and a text or JSON body
- The complete response back: status line, headers and body
- A User-Agent you set yourself, or one generated at random to constraints you give
Python. No account, no key. File writes can be confined to the client's workspace root when the client supports that capability, and are otherwise done by absolute path.
One command — pip install .