Buzzy Custom MCP
Last updated
Buzzy Custom MCP is the workflow for enabling MCP on an app you built with Buzzy. Once enabled, MCP-aware AI assistants can interact with that app's data and actions through Buzzy-generated tools.
Use this section when you want an app to be available to ChatGPT, Claude, or another MCP-compatible client. If you want an AI agent to build or edit the app itself, use Buzzy Builder MCP instead.
Buzzy generates MCP capabilities from the app you have already built:
datatable list, get, create, update, and delete tools
Buzzy Functions that are available as tools
widgets that can display app data inside an AI assistant experience
OAuth-based user authentication
the same server-side data access rules used by runtime and REST API calls
MCP tools follow the same server-side access and Private Data rules as the Buzzy runtime and REST API.
MCP calls authenticate as a Buzzy user.
Row access, Field view, and Field edit rules still apply.
Basic Private Data is masked or redacted when the caller should not receive the raw value.
Sensitive Private Data is hidden by default unless the caller has permission to access it through the relevant tool path.
Private Data image and file fields do not expose denied attachment metadata or signed URLs.
When enabling MCP for a compliance-oriented app, test with both allowed and denied users. Do not assume an AI assistant should receive more data than the same user would see in the Buzzy app.
Last updated