posted by chriskapp on
We are really proud to announce the next major version 6.0 of Fusio. This release is a great milestone for Fusio, with the new connection panels you can build now complete APIs within Fusio without the need to use an external tool. Through the MCP support there are now also many exciting possibilities how you can interact with Fusio. Our goal is to develop a platform which helps everybody to build great APIs. As usual the following list covers all important features of this release:
We have added an MCP server, it is possible to use the MCP server directly through stdio transport by using the php bin/fusio mcp
command.
There is also an experimental HTTP transport which you need to activate through the configuration.
To help LLMs understand our API we have added many descriptions to each operation and schema, which in the end now also help developers.
Fusio includes now a small OAuth2 authorization server which can be used to obtain an access token. This OAuth2 server can also be used by external apps i.e. if you use Fusio as backend for your single page application.
All internal apps now also automatically register the authorization server as identity provider so you can use it to login. In the future we may move completely to this authorization server.
To handle authentication with MCP we have implemented the oauth protected resource endpoint RFC.
We have added new designer panels for different connection types, i.e. the HTTP panel allows to execute HTTP requests and the filesystem panel allows to manage files.
We have moved the complete database endpoint under the connection which now works similar to the other connection designer panels. Note this is a breaking API change,
so you need to adjust your URLs in case you use this endpoint. Basically you only need to change the base path from /backend/database/:connection_id
to
/backend/connection/:connection_id/database
.
It is now possible to configure different captcha provider so that you can use an alternative to ReCaptcha. The captcha is used to protect your user registration.
In case you want to build an internal app you can deactivate the user registration.
We have improved the backend CSS layout so that it is more responsive for other devices like a tablet or smartphone.
If you want to provide some feedback take a look at our GitHub discussions or issues page. For more details and background information about the release you can also take a look at my personal blog, where I have published a post about the new 6.0 release.
Best regards
Christoph