Base44 Apps Publish New MCP Tools Without Reconnecting

Base44View original changelog

When a Base44 app publishes a new MCP tool, people already connected from an AI assistant now see it without reconnecting. The first call to the new tool asks them to approve it on the connection they already have.

Key Takeaways

  • New MCP tools show up without reconnecting, so people already connected from an AI assistant see them automatically.
  • The first call to a new tool asks for approval, keeping the connected person in control of what the assistant can do.
  • Approval happens on the existing connection, so nobody has to repeat the setup flow.
  • Builders can ship new app capabilities to AI assistants with a normal publish.
  • The change removes a friction point for iterating on an app's MCP tools.
  • It applies to Base44 apps that publish MCP tools to assistants.

New MCP tools appear automatically

Base44 apps can publish tools over the Model Context Protocol so that AI assistants can work with them. Until now, adding a tool to an app meant people who had already connected from their assistant had to reconnect before the new tool showed up. Base44 removed that step. When an app publishes a new MCP tool, everyone already connected sees it in their assistant straight away.

Approval on first use

New tools do not run silently. The first time someone calls a newly published tool, Base44 asks them to approve it on the connection they already have. This keeps the person connecting an assistant in control of what that assistant can do, while sparing them the work of setting up the connection again each time the app grows.

Why it matters

For builders who expose their app to AI assistants, shipping a new capability is now a single publish. Existing users pick it up on their next use, after a one-time approval, which makes iterating on an app's MCP surface much smoother.

Base44 MCP Tools Now Appear Without Reconnecting | Yet Another Changelog