Repository navigation
Mools 1.2.0
Mools now works offline, remembers your favorite tools and has a hardened MCP server. The project also has browser tests, a public roadmap and a complete set of community files.
Added
- Offline support. Mools can be installed as an app and every page works without a connection after the first visit (a web app manifest, icons and a service worker, about 8 MB). A banner explains when you are offline, and another offers a reload when a new version is ready. The Telegram tester says clearly that it needs the internet.
- Favorites. A star button on every tool page. Favorites appear at the top of the sidebar, on the home page and first in the command palette, and are kept in the browser.
- Browser tests (Playwright) that open every page and exercise the main tools, run by a new
CIworkflow on every pull request. The deploy workflow runs them too, so a broken page blocks it. - Community files:
CONTRIBUTING.md, a code of conduct (Contributor Covenant 2.1), a security policy, an accessibility statement and a support guide, plus an accessibility issue form. The repository's community standards checklist is complete. - A public roadmap: a project board, version milestones and tracked issues. New issues from the issue forms are added to the board automatically.
- MIT license and repository metadata (description, homepage, bugs and license) in
package.json. - A
Releaseworkflow that publishes a GitHub release when a version tag is pushed. Release tags are signed.
Changed
- MCP server: tool calls run in a worker thread with a 15 second limit, and arguments are checked against each tool's schema, with readable messages for wrong types, bad values and out-of-range numbers. Unknown arguments are now rejected, because the schemas already said they were not allowed.
- MCP clients, note:
cron_explainnow reports thetimeZoneand returns every run as an object withutcandlocaltimes;nextRunsused to be a list of UTC strings. - The logo and screenshots are about 21% smaller; every pixel is unchanged.
Fixed
- A regular expression with catastrophic backtracking, for example
(a+)+$, froze the MCP server for good. Such calls are now stopped after 15 seconds and the server keeps answering. (The web tools that take a pattern can still freeze the tab; this is tracked in #20.) - Passing the wrong type to an MCP tool gave a raw JavaScript error such as
text.normalize is not a function.
Full changelog: v1.1.0...v1.2.0