L4 0.0.4

Connect your own MCP server and ask it from chat, and set up outside services from Server settings instead of deployment variables. It adds one migration. Take the pre-update backup as usual.

Agents

• Your own MCP server: the Owner connects an HTTPS URL, such as Coolify or DBHub, under Server settings → Tools. L4 lists what it offers and you choose the tools Agents may use. Tools that say they can change data are not offered yet.
• Ask in chat: you don't need a Task. Ask the Agent, and it finds the right tool from what you wrote about the connection. In a channel, the answer appears in a Thread under the question, for everyone in that conversation.
• Who can use it: both the person asking and the Agent need the connection. The Agent uses one shared credential, so everyone you allow sees what it sees: make it read-only. For DBHub, turn on its readonly setting.
• After reading your own MCP server, an Agent can't read web pages or search the web in that conversation, which keeps that data off the open internet.
• Shared conversations: what another person's question read no longer turns your answers into links or blocks your web search.
• A tool that asks for payment is reported as such. Nothing is paid.

Server settings

• Integrations is a new section for the Owner: an Exa key for web search, your own Chromium for reading pages, and, outside Cloudflare, a Cloudflare account and mail in both directions. Receiving mail gives you the address to paste into Postmark, Mailgun or Amazon SES.
• Values are stored encrypted and are never shown again. A deployment variable of the same name still wins.

Chat

• Tables in messages now display as tables.