Fresh approach to serving tools via FastMCP #236
Description
We have trialed switching tool-vault-packager to FastMCP. But, the legacy REST-based strategy is too deeply intertwined.
We;re going to adopt a fresh strategy.
We'll create a new package, under apps. This will be ToolsMCP. Create the package, and configure it as a python package. Copy the tools folder from libs/tool-vault-packager into this new package.
Then introduce a root level file which will create a python-based FastMCP server, and serve the above tools.
We will add the MCP Inspector app to the package, that will be used to inspect/verify the MCP server, and its tools.
The build process will package the server into a wheel, and into a .pyz file (like in tool-vault-packager) - for distribution in, and exploitation by our vs-code extension.
Refer to libs/tool-vault-packager readme and CLAUDE.md for tips on pulling in dependencies, and configuring the build to suit delivery in a dockerfile.
Later, we will connect our vs-code front-end to the server.