Consider adopting FastMCP

[punkpeye]

The main benefit of FastMCP is that it cuts down on the boilerplate code for setting up tools, prompts, resources, error handling, etc.

Here is an example PR showing how much code is reduced by adopting FastMCP: https://github.com/pskill9/website-downloader/pull/2/files

All the code maps directly to your existing implementation. The only consideration is that FastMCP uses Zod instead of JSON schema.

Additionally, FastMCP enables SSE transports, which is great to future proof your MCP server.

If you are open to it, I would be happy to raise a PR that does the migration.

[jirispilka]

I'm sorry for the delayed response.

Thank you for your interest in this MCP; I appreciate it.
This MCP was the initial solution.

I have since moved certain parts of the code to the [RAG Web Browser Actor](apify/rag-web-browser#40) so that the server can run in the cloud. In that implementation, I'm using JSON schema.

Additionally, I'm in the process of creating an [MCP server for all Apify's Actors](https://github.com/apify/actor-mcp-server/tree/feat/implementation) (work in progress). I'm also using JSON schema there.

I might eventually update this MCP in a similar way, but I'm not certain yet.
I really appreciate your offer, but I don't think it's worth investing time into refactoring it at this point.

Thank you again for reaching out.