v0.26.0

Connectors

7 more adapters in the catalog: 380 in total, up from 373 (#1053). We picked them from catalog searches that found nothing and from connectors that workspaces had built by hand.

• Facebook Pages.
  • What it covers: posts (including scheduled and photo posts), comments and replies, Page and post insights, and Messenger conversations within the 24-hour window.
  • Insights only use metrics that Meta still supports.
• Google Gemini API. Text and multimodal generation, token counts, embeddings, image generation and editing, and files.
• OpenAI API. Responses, image generation and editing, embeddings, moderation, files and batches.
• Cloudinary.
  • Upload from a URL to get a public link, manage assets and folders, search, transformations, and AI image generation.
  • It runs through Cloudinary's official MCP server, and sign-in takes one click.
• TED. EU public tenders: search, count and fetch notices. No key needed.
• Mirakl Seller API.
  • One install per marketplace.
  • It covers orders (accept, ship, tracking), offers, products, messages, returns, shipping zones, invoices and transactions.
• Trendyol.
  • It covers products, orders, returns, customer questions, categories and brands, and finance.
  • It already uses the new order list (/v2/orders) and Product v2 filters, because Trendyol switches off the old order and product lists on 15 Oct 2026.

Safety. Publishing, messaging, AI image generation and marketplace writes ask the model to confirm with the user first. Deletes, and Mirakl's offer file import in replace mode, are installed switched off.

Images in tool results

A tool can now return images to the AI client (#1053).

• Setup. Turn it on by setting responseMapping.images to a base64 field.
• What gets passed through. PNG, JPEG, GIF and WebP, recognised from the file's own bytes.
• Limits. Up to 4 images per result by default (10 at most) and 4 MiB per image.
• Fallback. The text answer keeps a short placeholder for clients that don't display images.
• Compatibility. Tools without the setting behave exactly as before.

Catalog search

• One search everywhere. Search in the store, on the welcome page and in chat setup now uses the same matching (#1051).
• Typos. "telgram", "esty" and "shopfy" now find Telegram, Etsy and Shopify. Filler words such as "bot de" or "für" are ignored.
• Aliases. Adapters can declare aliases, and 24 do: amoCRM finds Kommo, Mercado Livre finds Mercado Libre, Twitter finds X, Sendinblue finds Brevo, OTRS finds Znuny, plus D365, GA4, SAP B1 and others.
• Ranking. Exact matches always rank first. Typo matches come after them and are capped.

Secrets stay out of URLs and tool names

Credentials no longer end up in plain text in a connector's address, its paths or its tool names (#1054).

• What is detected. Bot tokens, API keys, JWTs and credential query parameters written into a URL or path. This applies when you create or edit a connector or tool, import OpenAPI, Postman, cURL or JSON, or restore a backup.
• What happens to them. They move into an encrypted connector variable, and the URL keeps a {{VARIABLE}} reference. The app tells you which variable it created, without showing the value.
• Tool names. Names generated from a path no longer contain the secret.
• Catalog installs. Telegram, Z-API and Bitrix24 now store the variable reference instead of the token in the connector address.
• Error logs and the invocation log. These mask the connector's own secret values. Sentry also masks keys found in URL paths.

Self-hosted

• Database: no migration.
• Existing connectors: connectors with a secret already written into their address keep working unchanged. Editing them moves the secret into a variable. A repair script (packages/backend/scripts/secret-literals/repair.ts) can do this for all connectors at once. It is a dry run unless you pass --apply, and with --apply it takes a backup first.
• Docker image: helpcodeai/anythingmcp:v0.26.0.