AnythingMCP 0.54.0: restricted member visibility, Instagram sign-in with Meta, WooCommerce one-click keys

This release collects everything merged since 0.53.0. The main addition is a workspace setting that limits what members who are not admins see in the dashboard and the REST API. It also brings sign-in with Meta for the Instagram connector, a one-click key flow for WooCommerce, catalog updates that apply themselves when they only add optional parameters, and a set of fixes and dependency updates. The catalog has 732 connectors.

Member visibility

• New setting: Settings → Organization → Member visibility (Open / Restricted). With Restricted, a member who is not an admin sees only what their AI client can use (#1664, #1665, #1666, #1667, #1668):
  • Logs and analytics: only their own tool calls, without the usage-by-user breakdown.
  • Connectors and tools: only connectors they own or that hold at least one tool their MCP roles allow, and of those only the allowed tools. Exports cover their own connectors only.
  • MCP servers and the server picker: only servers they own or that hold one of those connectors, in the dashboard and on the consent page.
  • A connector or server they cannot see answers 404, the same as an unknown id.
  • Admins always see everything. The MCP endpoint is unchanged: roles already decided there which tools an AI client gets.
• Open is the default, and nothing changes until an admin switches it. Same in every edition, Cloud and self-hosted. A change is recorded as a MEMBER_VISIBILITY_CHANGED security event.
• API: GET /api/settings/member-visibility and PUT /api/admin/settings/member-visibility (also available as amcp api operations). Guide: docs/operations/member-visibility.md. It walks through roles with tool lists, Viewer members, mapping SSO groups to roles, and then switching to Restricted.
• Viewers can no longer create MCP servers (403, like every other write a Viewer tries). The buttons to add connectors or servers are hidden for Viewers (#1667, #1668).
• The Roles page and the roles API now say what a user without an MCP role gets: every tool while no role has a tool list, no tools as soon as one role has a tool list (#1662, #1669).

Connectors

• Instagram: sign in with Meta (Unified Login, no token to paste). It works with a Meta app of your own, or with a server-wide app set in META_PLATFORM_APP_ID / META_PLATFORM_APP_SECRET / META_PLATFORM_CONFIG_ID. The new META_PLATFORM_ORG_IDS limits the server-wide app to some workspaces, for example while the Meta app is still in review (#1630, #1660). Deleting an Instagram connector with a long call history no longer times out (#1641).
• WooCommerce:
  • One-click key: the shop owner approves access in WooCommerce and the key is stored for the connector. Off by default, enable it with WOOCOMMERCE_ONE_CLICK=true (#1633).
  • Guided setup: the setup explains each step and flags a key the shop keeps refusing (#1634).
  • Smaller list results: orders and products come back as compact list results by default (#1635).
• Amazon: report files are downloaded and read on the server, and finance tools were added (#1645). Rate-limit notes corrected (#1648, #1651).
• DC Hub: bridged to DC Hub's official MCP server (#1629).
• Fixes:
  • FileMaker: get_record uses recordId, and database names with spaces are documented (#1640). Thanks @GallaGit.
  • SAP Business One: the valid journal origin names and item fields are listed (#1646).
  • Falabella: order filters fixed (#1628).
  • Substack: cursor paging fixed (#1628).
  • Gemini: empty answers fixed (#1628).

Catalog and engine

• Catalog updates that only add optional query parameters are applied to installed connectors automatically. Other changes still wait for "Apply update" (#1631).
• Catalog resyncs of large connectors at startup get 30 s per transaction, so they no longer skip (#1643). Updating a connector reads only what it needs (#1627).
• OAuth 2.0 with client_secret_basic no longer also sends client_id in the body. Some providers refused the token request because of it (#1653).
• Tool names are trimmed of surrounding spaces and tabs on create, update and bulk create (#1655).
• Tool outputs that contain functions are stored as a plain JSON copy in the audit log instead of being dropped (#1642).
• Knowledge graph edges are indexed by node, so deleting a connector no longer scans the whole table (#1639; two index migrations, applied automatically at startup).

Security

• An OAuth refresh grant is refused for an MCP server of another workspace (#1632).
• Dependencies:
  • @hono/node-server 2.1.8 through the MCP transport (#1654).
  • hono (#1658), basic-ftp (#1657) and fast-xml-parser (#1636).
  • soupsieve 4.0.1 in the file extractor (#1661).

Upgrading a self-hosted instance

1. Update the compose file and .env.example from this release (git pull, or download them from the release tag).
2. docker compose pull && docker compose up -d. The database migrations run on their own at startup.
3. If you use File Search (the files profile), the file extractor image is now tagged 3, and docker compose --profile files up -d builds it on first start.
4. Optional new settings in .env: META_PLATFORM_ORG_IDS, WOOCOMMERCE_ONE_CLICK (see .env.example).
5. To use member visibility: Settings → Roles (give each role its tool list), make members Viewers, then Settings → Organization → Member visibility → Restricted.

The CLI is released separately as cli-v0.1.6 (npm i -g @anythingmcp/cli), with the member visibility operations in amcp api.

Full changelog: v0.53.0...v0.54.0

New routes since 0.1.5, released with AnythingMCP 0.54.0.

• amcp api --list and the shell completion know the member visibility routes (#1664):
  • GET /api/settings/member-visibility: the workspace's mode (open or restricted) and whether it narrows your own view;
  • PUT /api/admin/settings/member-visibility: switch it (workspace admins), for example amcp api PUT /api/admin/settings/member-visibility --data '{"mode":"restricted"}' --yes.

npm i -g @anythingmcp/cli@latest

AnythingMCP 0.53.0: management API and CLI, per-tool rate limits, tighter API keys, 731 connectors

This release collects everything merged since 0.52.1. Version 0.52.2 was tagged without release notes, so its changes are listed here too. Main additions: a management API with the amcp command-line client, per-tool rate limits and latency stats for MCP roles, a webhook dashboard, stricter API key handling, and a catalog that grew from 694 to 731 connectors.

Management API and the amcp CLI

• Management-scoped API keys: a key can now be issued for the management API (/api/*), read-only or read-write, separate from MCP keys. MCP keys are refused on /api, and read-only keys cannot write (#1508).
• amcp CLI (npm i -g @anythingmcp/cli or brew install helpcode-ai/tap/amcp): browser login, MCP tool calls with JSON output, and amcp api for every management route, with a built-in route list (amcp api --list). Released separately as cli-v0.1.5 (#1508, #1514, #1515, #1520, #1524, #1525, #1572).
• The management API is documented in Swagger with real examples. Routes for the browser only are hidden from Swagger (#1528, #1558).
• Connector exports made with a read-only key never contain secrets, and exporting a connector from another workspace answers 404 (#1525).

Roles, limits and monitoring

• Per-tool rate limits for MCP roles: set them in Settings → Roles. A refused call is logged with the limit that refused it (#1544, #1556). Thanks @Coding-Professional.
• Per-tool latency and error rate in the audit view (#1521). Thanks @wunsir.
• Webhook dashboard: recent inbound events and the delivery URL of each connector with inbound webhooks (#1571). Thanks @rangarajan19.
• The tool registry is indexed by workspace and connector, and server/discover answers without the tool list. This keeps a burst of client handshakes from slowing down large instances (#1478).

Security

• API keys are scoped to the workspace they were created in. Before, a key followed its owner's active workspace and role (#1622).
• Per-user API keys are hashed at rest (keyed HMAC). Lookups use the hash (#1555).
• An MCP server's sign-in refuses a user from another workspace (#1609, #1613).
• Accounts must confirm their e-mail code before they can approve an AI client's access (#1566), and the sign-up code is checked on Enter (#1536).
• The app is kept out of search engines, except the Cloud sign-in page (#1562).

Connector engine

• loginBasicAuth for LOGIN_TOKEN logins: the login sends HTTP Basic built from username and password, for APIs such as Wazuh and the FileMaker Data API (#1460). Thanks @GallaGit.
• Token paths may point into a list (#1570), and query strings can be signed with sorted-query HMAC (#1543).
• A REST call that used up its whole deadline is not sent again (#1502). The "gave up" warning shows the HTTP status (#1505).
• Numeric limits and array item values of tool schemas reach the AI client (#1470).
• Installed catalog connectors send the catalog User-Agent (#1539).
• A __proto__ key stays data when a tool-call log excerpt is cut (#1469). The MCP in-flight gauge settles for clients that hung up early (#1577).
• Catalog search caps query length and trims words without a regex (#1501).

Connectors

• New:
  • from the community: Claris FileMaker (Data API, read-only, #1624, @GallaGit), Wazuh (#1461, @GallaGit), Faire (#1563, @aj-codespy), Factorial HR (#1534, @Aadithya-kl), Pixabay (#1468, @ak-bharadwaj), Podio (#1479, @ZYZ666-RGB);
  • from the team: TikTok Shop Seller (#1523, #1535), Falabella Seller Center (#1543), Grupo Éxito Marketplace (#1570), 15 adapters for helpdesk, company data, sports, fleet and market data (#1540), and catalog block 29: company registries, bol.com, Cin7, Tookan, Threads, NinjaOne, Housecall Pro, Egypt ETA (#1614).
• Widely used operations added to 16 adapters, among them eBay, Amazon, Mercado Libre and Etsy (#1541). Fudo gets expense, category and provider fields, plus stock and supplier tools (#1517).
• Handelsregister now uses the handelsregister.ai v1 API (#1606). Apify follows its MCP server 0.21 tool list (#1552). Ghost Admin API tokens are signed for each request (#1615).
• Clearer hints and limits for:
  • Etsy: tag length, title length, large offsets (#1471, #1503, #1527, #1553, #1569);
  • weclapp, Business Central and SAP Business One fields (#1476, #1549, #1569, #1619);
  • WooCommerce order lists, Mercado Libre visits, Printify pages and the eBay probe (#1504, #1578, #1619);
  • Odoo partners without the Invoicing app (#1597).
• Playtomic connectors are unlisted: Playtomic's login now needs app attestation (#1506).
• The Deepgram logo follows the new brand (#1616). Thanks @mwygant-dg.

Self-hosting

• A Docker Compose file for Coolify deployments (#1328). Thanks @flyingwebie.
• The files worker boots without Redis (#1526).
• Account and workspace deletion get a 60-second transaction timeout (#1567).
• File Search maintenance runs per workspace under row-level security (#1557).

AnythingMCP Cloud

These changes concern cloud.anythingmcp.com. Self-hosted instances are unchanged.

• Plans: the trial gets Team limits for File Search and code mode (#1599). Moving to Starter shows what changes before checkout, and items above the new plan's caps are paused, then restored on upgrade (#1601, #1602, #1603). Connectors with inbound webhooks are capped per plan (#1612). Code runs have a monthly cap and a per-workspace concurrency limit (#1492).
• Billing: each paid invoice is e-mailed as a PDF, and amcp invoices email switches it on or off (#1604). A link to the Data Processing Agreement is under Settings → License (#1511). Plan changes made on the licence site reach Cloud within seconds (#1560, #1561), and paid licences bind to their workspace within minutes (#1542).
• Setup: checks find the Odoo database name and test the address before a chat install (#1607, #1610). The YouTube API key field explains itself and refuses OAuth values (#1608). Servers that only accept approved IPs are shown the fixed outbound IP (#1487, #1493).
• Ended trials: the trial wall shows the workspace's own numbers, can switch workspace, and preselects the fitting plan. A no-login reactivation page serves blocked calls (#1475, #1497, #1573–#1576).
• ChatGPT: the AnythingMCP plugin and a File Search plugin with folder setup during authorization are listed in the ChatGPT plugin directory (#1486, #1494, #1545, #1546, #1550).
• Support chat: it can set up a connector, for example Telegram from a pasted bot token, and tells customers when a person takes over (#1583, #1585, #1623, #1625).

Docs

• The connector catalog by category (docs/catalog) and a catalog page for each connector: how to start without code, how it works, and every tool (#1548, #1554).
• Use-case guides for Odoo, Etsy and SFTP/FTP with Claude, and a CLI announcement guide, in English, German and Italian (#1514, #1516).

Other

• Dependency updates: Next.js 16.4.5, @nestjs/swagger, openid-client, imapkit, jmespath, pino-pretty, @azure/identity (msal-node 7.2.1) and others.
• CI boots the backend and the files worker from the build on every PR, and the CLI is tested on Linux, Windows and macOS (#1532, #1537).

Thanks to everyone who contributed to this release: @GallaGit, @Coding-Professional, @wunsir, @rangarajan19, @aj-codespy, @Aadithya-kl, @ak-bharadwaj, @ZYZ666-RGB, @flyingwebie and @mwygant-dg.

Docker image: helpcodeai/anythingmcp:v0.53.0

New commands and routes since 0.1.4, released with AnythingMCP 0.53.0.

• amcp invoices email [on|off] [--to <address> | --billing-contact] (AnythingMCP Cloud, workspace admins): shows whether each paid invoice is e-mailed as a PDF, switches it on or off, and changes the recipient. It asks before changing anything; pass --yes in scripts (#1604).
• amcp api --list and the shell completion know the new management routes:
  • per-tool rate limits for roles (#1544, #1556);
  • the webhook dashboard: recent events and delivery URL (#1571);
  • Cloud plan fit: what a workspace keeps on Starter or Team (#1601);
  • invoice e-mail settings (#1604).
• Install with Homebrew: brew install helpcode-ai/tap/amcp (#1572).

npm i -g @anythingmcp/cli@latest

Fixes found while testing the CLI end to end against AnythingMCP Cloud (#1525), plus #1524 and the new README (#1528).

• amcp --version / -v.
• amcp api shows the server reason on 401/403, e.g. Forbidden (403): This API key is read-only.
• amcp api GET … --data is refused with a clear message instead of a misleading connection error.
• One profile can hold both an MCP key and a management key: logging in with one keeps the other for the same instance.
• MCP errors tell a rejected key (401) from a key not allowed on that server (403).
• amcp api --list marks admin-only routes correctly.
• Windows: the browser login opens without cmd start (#1524).

Server side (already live on Cloud): connector exports made with a read-only key never include secrets.

npm i -g @anythingmcp/cli@latest

Fix: amcp login --browser now completes against HTTPS instances such as AnythingMCP Cloud. Browsers send Origin: null when the HTTPS dashboard posts to the http://127.0.0.1 loopback, and the CLI had rejected that request with "Unexpected origin" (#1520).

npm i -g @anythingmcp/cli@latest
amcp login --browser --url https://cloud.anythingmcp.com

Maintenance release of @anythingmcp/cli — same features as 0.1.0, now published to npm via OIDC trusted publishing (no long-lived token).

npm i -g @anythingmcp/cli
amcp --help

First public release of the AnythingMCP CLI (@anythingmcp/cli, bin amcp).

• Call MCP tools from the terminal: amcp login, amcp tools ls/describe/call.
• Drive the management API with a management-scoped key: amcp api <METHOD> <path>, amcp api --list.
• Browser login: amcp login --browser mints a management key via the dashboard over a loopback.
• Shell completion for bash, zsh and fish.

Publishing this release runs the publish-cli workflow, which publishes the package to npm.

AnythingMCP 0.52.1: smoother setup from the chat, code mode fixes, 3 new connectors

A maintenance release on top of 0.52.0. It makes adding apps from Claude and ChatGPT smoother, fixes self-hosted code mode, simplifies the self-hosted editions, and adds three catalog connectors.

Self-hosted editions: Community and Enterprise

• Community is free under AGPL-3.0 for any use, including commercial use, for up to 3 active users with unlimited connectors and MCP servers.
• Enterprise (on request) adds more users, single sign-on, SCIM, File Search beyond the trial and support. Admins can try single sign-on and SCIM for 30 days under Settings → License.
• Self-hosted Starter and Team are no longer sold. Existing Starter and Team licence keys keep working as before (#1467).
• The 30-day File Search trial on Community now starts with a registered licence key; the free Community key from Settings → License counts. Trials already running are unchanged (#1466).
• When a self-hosted instance verifies its licence key, it now also sends the AnythingMCP version and the number of active users, connectors and MCP servers. No connector content, tool calls or user data. Set LICENSE_USAGE_REPORT=false to turn this off (#1466).

Setup from the chat

• After you connect an AI client, the authorization page offers the first app to add for the workspace you picked, and one-click installs no longer fail when an app needs an address (Shopify, Odoo, WooCommerce, Telegram): the connector is saved as a draft that asks for the missing values (#1449, #1450).
• Setup links from the chat open the dashboard without a second sign-in, in the link's workspace, and the sign-in page offers "Continue as …" for two hours after an AI client sign-in (#1452, #1456).
• Address fields add a missing https://, and Odoo below version 19 gets a one-click switch to the JSON-RPC connector (#1453).
• Chat setup in a workspace without a licence now says so instead of asking to remove a connector (#1448).
• Connector search ranks the app a search word names first, and no longer lets File Search entries crowd it out (#1458, #1464).
• The app picker after authorization no longer offers Google Gemini (#1465).

Code mode (self-hosted)

• Three self-hosted code mode bugs fixed, code mode can be switched per MCP server, and code tools follow the plan limits (#1444, #1445, #1446, #1447).

Connectors

• New: Pipefy (#1373), SumUp (#1367) and Football Charts (#1454).
• eBay sellers sign in instead of pasting a refresh token (#1430); Etsy keys are kept while the app waits for Etsy's approval, and the owner gets an email when Etsy approves it (#1432, #1440); Atlassian API tokens are checked at setup (#1442).
• Catalog tools that declare no parameters are installed again (#1435); MCP bridge tools receive only the variables their schema declares (#1443).
• Connect attempts get 3.5 s, so a resent SYN can land (#1436).

File Search

• Text extraction for 103 file types, pages and images shown to the AI as pictures, file links every AI client can open, calmer syncs when the extractor restarts, and folder rules that match the Files panel (#1399, #1400, #1401, #1402, #1417, #1419, #1433).

Other fixes

• Errors that kept connectors stuck are explained or refused with a clear message (#1437).
• Chrome's "network error" counts as a lost connection (#1434).
• The onboarding reminder run skips a user deleted while it runs (#1462).
• Dependency updates: MCP core 2.4.0, NestJS, Next.js, AWS SDK and others.

Docker image: helpcodeai/anythingmcp:v0.52.1

AnythingMCP 0.52: your AI can now search your files and write code

The biggest release since the project started. Two new capabilities change what an AI client can do through AnythingMCP:

• File Search gives Claude, ChatGPT, Gemini, Microsoft Copilot, Cursor and Muse a searchable index of your company folders on SFTP, FTP/FTPS, WebDAV (Nextcloud, ownCloud, NAS), S3 or a mounted network share.
• Code Mode lets an AI client run one short program that calls several tools, so a five-step lookup becomes one call. It runs in an isolated sandbox that has no secrets and no network access.

Plus German and Italian across the whole app, an IMAP/SMTP e-mail connector, inbound webhooks, per-user sign-in for OAuth connectors, and 130 new catalog connectors (561 → 691).

📂 File Search: ask your AI about the documents on your file server

Point AnythingMCP at a folder. It reads every PDF page, every Excel row with its column names, Word, PowerPoint, Outlook .msg and .eml files with their attachments, and keeps that index in sync. Your AI client then gets nine tools for each folder:

So a question like "what does article NT-601 cost in the current price list?" takes seconds, with the file name, page and date in the answer.

A setup that guides you. Connectors → New → File Search opens a five-step wizard:

1. Source: pick the protocol and enter the server.
2. Test: AnythingMCP connects before anything is saved and shows a checklist. SFTP host keys and self-signed certificates are pinned by fingerprint.
3. Scan: a dry run lists the folder: files per subfolder, file types, years. Archive folders start unticked, and a budget bar compares your selection with the plan.
4. Describe: a draft of the connector's description that every AI client reads. AI writes it if you enable that; otherwise it comes from rules.
5. Activate: the first sync starts right away.

Built so it never gets in the way:

• Syncs run in a separate files-worker process, never in the server that answers your AI clients.
• Big first syncs go in slices, so other workspaces keep their turn.
• Only new and changed files are downloaded (size and modification time, ETag, SHA-256).
• When a folder outgrows the plan, the sync pauses before downloading anything. The index stays searchable, and the Files panel shows what to do.

Secure by design:

• Every query is filtered by workspace, and the database enforces it again with Row-Level Security.
• Credentials are decrypted only in the worker.
• The text extractor runs on an internal network with no route out, read-only and without capabilities.
• On Cloud, the SSRF policy checks every address, redirect and passive FTP data connection.
• Enterprise adds folder permissions per role and a workspace policy: public links, AI drafting, plain FTP.

File Share:

• Temporary download links for files from your folders, or for files an AI client writes (a CSV export, a report), through the File Share connector.
• Internal links work only for members of the workspace; public links work for anyone who has the link.
• Each link has an expiry; only a hash of its token is stored.
• Downloads go through 60-second signed URLs and are always served as attachments.
• Settings → File Share lists every link, with search, filters and revoke.

In the marketplace: SFTP, FTP/FTPS, WebDAV, S3 bucket, Nextcloud, ownCloud, Synology NAS, QNAP NAS, Fritz!Box storage, Hetzner Storage Box and Network folder (self-hosted). Each opens the wizard with the right settings already filled in.

Plans:

Self-hosted needs a paid licence or the 30-day trial. The sync engine and the extractor are under the AnythingMCP Commercial License (ee/).

Self-hosted setup: add FILES_WORKER_URL, FILES_WORKER_TOKEN and FILE_EXTRACTOR_TOKEN, then start the files Compose profile. Details are in docs/connectors/file-search.md. (#1379–#1389, #1395, #1397)

🧩 Code Mode: one program instead of ten tool calls

An AI client can now write a short JavaScript program that calls several MCP tools and combines the results. It replaces a long chain of separate tool calls.

• Isolated runner. A separate code-runner container starts one Deno subprocess per run. The subprocess has no network, no files and no environment variables, and never sees a secret. The only way out is amcp.search, amcp.describe and amcp.run, and each of those calls goes through the caller's roles and permissions, like a direct MCP call. There are wall-clock and output limits, and a containment test ships with the runner.
• Saved code tools. An admin can save a program as a tool (endpointMapping.method: "code") with its inputs, the connectors it may use, and invoker or definer rights. It is then available like any other tool: audited, governed by roles, exportable.
• Inline code_execute. A per-server switch (off / tools / inline) and a per-role capability decide who may run ad-hoc programs.
• Agents can propose code tools. code_propose_tool files a proposal, which an admin reviews and approves in the UI. Nothing runs until it is approved.
• Code tools are never served on the shared /mcp endpoint.

Run it with the code-runner Compose profile and CODE_RUNNER_URL. See docs/code-mode.md. (#1366, #1369, #1370, #1377)

🌍 The app in German and Italian

The app is translated into German (formal Sie) and Italian: dashboard, connectors, marketplace, MCP servers, settings, audit log, analytics, knowledge graph, skills and memory. Untranslated text falls back to English, never to a raw key. (#1272, #1274, #1283, #1303, #1318, #1325, #1326, #1332, #1333, #1340, #1360)

More new features

• E-mail connector (IMAP/SMTP). Read, search, file and send mail with any mailbox: IONOS, Strato, GMX, web.de, T-Online, Gmail with an app password, or your own server. (#1348)
• Inbound webhooks. Connectors can receive webhook events; Stripe is the first. A built-in tool lets the AI read recent events. (#1372)
• Per-user sign-in for OAuth2 connectors (Enterprise). Each user connects their own account, so the AI acts with that user's rights. (#1302)
• Per-tool timeout and response size for REST tools, for slow or huge upstream APIs such as image generation. (#1378)
• Setup links with prefilled fields (prefill.<NAME>), so a partner integration can send users to a half-filled setup. (#1334)
• Payment connectors serve their read tools on the shared endpoint. (#1345)
• AliExpress Affiliate and Dropshipping with IOP request signing. (#1346)

130 new connectors

561 → 691 catalog adapters, including n8n, Hostinger, GoDaddy, Strapi 5, Gitea, Home Assistant, SonarQube, Immich, deed.page, DHL Parcel DE shipping, Billbee write tools and the File Search entries above, plus five blocks of AI, scraping, research data, CMS, HR, field service, POS, hotel, office, BI, developer tools, operations and secrets connectors. (#1304, #1342, #1343, #1350–#1353, #1356, #1275, #1285, #1307, #1317, #1327, #1329)

Fixes and hardening

• MIME display names are parsed without a polynomial regex. (#1357)
• E-mail addresses are masked in every backend log. (#1359, #1375)
• Each outbound connect attempt gets one second instead of 250 ms. (#1376)
• OpenAPI imports parse only OpenAPI documents and resolve only internal refs. (#1291)
• The tool response size is capped, and the rendered result is capped too. (#1279, #1298)
• The tool response cache is keyed by tool id and nested params. (#1308)
• Same-named tools of every connector are listed on a server. (#1309)
• PostgreSQL queries are retried without statement_timeout behind PgBouncer. (#1323)
• Etsy, Telegram, Odoo, Printify and weclapp tool fixes. (#1311, #1324)

Upgrading

• Migrations: code_mode (roles, MCP servers, code runs), webhook ingestion and file_search (seven file_* tables with Row-Level Security and the role amcp_files). They run automatically on start. The database user must be allowed to create a role: the default Compose setup is.
• New optional services, each behind its own Compose profile: code-runner (profile code-runner), and files-worker plus file-extractor (profile files). Nothing new starts unless you enable a profile.
• Node.js ≥ 22.15 when running from source. The Docker image is unaffected.

Full changelog: v0.51.7...v0.52.0