Can I connect an external AI assistant to Govform?

Yes. Govforms MCP lets a compatible AI client work with the platform through structured tools and explicit access choices.

MCP, the Model Context Protocol, supports working from an external assistant or building a controlled agent workflow. Darcy provides the AI experience inside Builder; an MCP client provides its own experience using the operations available to its connection.

Connect the work to the right permissions

Interactive sign-in. Connect an MCP client using OAuth, sign in to Govforms and select the libraries needed for the task.
Independent access choices. Choose no access, read-only or full access for form designs and Response Hub data separately.
Role-based limits. The connection follows the signed-in person's current library role; full access does not bypass it.
Server-side integration. Library-scoped API-key MCP is available for controlled server workflows, with separate operation permissions.

Use tools suited to the task

Depending on the grant and discovered tools, a client can find services, inspect their structure, make design changes or prepare publication steps. With the separate required permission, it can also work with supported Response Hub operations.

Each client's available tool catalogue determines what it can do. Some operations need additional permissions or a human approval step. Inspect changes in Builder and test the resulting service before release.

MCP tool calls use API units according to the operation. The reference explains the charging tiers and wider capabilities.

See Connect AI clients with Govforms MCP for endpoints and connection steps, or Govforms MCP capabilities for the reference.