Repository navigation
v0.55.1: stored database passwords moved at start, reduced view for restricted members
AnythingMCP 0.55.1: stored database passwords moved at start, a reduced connector view for restricted members
A patch release with two security changes for workspaces with several members, plus everything merged since 0.55.0. There is no database migration.
Security
- Database passwords saved before 0.55.0 are moved at start. 0.55.0 began storing the user name and password of a DATABASE connector in the encrypted
authConfigwhen the connector is saved. Connectors saved earlier kept them in the stored connection string until someone saved them again. The server now does this itself at every start, with the same rule as a save, and writes one log line:Database connection strings: credentials of N connectors moved into the encrypted auth config (…); N left as is (…); N failed. A second start finds nothing left to move. - Members in a restricted workspace get a reduced view of a connector they do not own. With Member visibility: Restricted, a member who is not an admin saw a visible connector in full: address, settings, instructions and the SQL of its tools. They now get its name, type, status and the tools their roles allow (name and description), in the dashboard and in the API (
GET /api/connectors,/:id,/:id/tools,health-check)./:id/oauth-configanswers 404 for them. Which connectors are visible has not changed: the ones they created, and those with at least one tool their roles allow. Admins, owners and workspaces in Open mode are not affected. See Member visibility. - Edit, Test connection and Variables are shown only to the connector's owner and to admins, in every mode. Before, the forms opened for everyone and the save was refused.
- Connection strings in the catalog update preview and in two log lines are masked.
- Public upload links accept only the canonical signature (#1733).
COOKIE_SECRETcan be added to a running installation without interrupting sign-in or connect flows in progress: cookies signed withJWT_SECRETare still accepted (#1737).
Fixes
- "Test connection" on a DATABASE connector resolves
{{VAR}}references in the connection string, as a tool call does. - The tool import accepts a spec address written without
https://(#1734).
Also in this release
- File uploads from the chat: an upload box in the AI client and an upload page for
file_upload_link(#1738). - Telegram: Telegram Web as a way to finish the one-tap setup on a computer (#1736).
- 848 connectors in the catalog (from 825): 19 regional marketplace connectors, the OpenCart Bridge connector (#1732), Apaczka, two more Mirakl retailers (The Range, Roman), and a refreshed DC Hub connector with 96 tools (#1672). HMAC adapters can sign requests inside a form body.
- Mirakl: an optional
shop_idon every Mirakl tool, for sellers with several shops, and tools to export offers (#1743). - CLI: the README shows how to manage learning projects (#1735). The CLI itself stays at 0.1.7.
- Cloud only:
PLAN_CAPS_ENFORCEreaches the backend container (#1739).
Upgrading
docker compose pull, thendocker compose up -d. No migration runs.- After the first start, look for the
Database connection strings:line in the server log. Connectors listed as "left as is" keep their credentials in the stored string, masked in every response: this applies to a multi-host MongoDB URL, a string that is not a URL, and one that uses{{VAR}}references (which hold no secret). - Change the database passwords that were written in a connection string before 0.55.0 if your workspace has members who should not have known them: until 0.55.0 the full string was shown to every member who could open the connector.
- Not covered by the reduced view yet: File Search connectors. A restricted member who can see one can still read its source and file tree through the API.