Connect AI clients with Govforms MCP
Govforms MCP lets a connected AI client inspect and manage the platform through structured, permission-aware tools. Use it when you want to work from an external assistant or build a controlled agent workflow.
How MCP fits alongside Darcy and the REST API
Darcy is the assistant inside Builder. MCP, the Model Context Protocol, exposes tools and guidance to an external client, which supplies its own AI experience. The REST API serves integrations that call defined endpoints directly.
A connected client can discover the tools available to its connection, read product and model guidance, and invoke authorised operations. The client's tool catalogue determines what it can actually do; it is not a promise that every Darcy interaction is available externally.
Connect interactively
For a person working in an AI client that supports MCP with OAuth, connect to:
https://govforms.uk/builder/mcp- Add the MCP server in your client.
- Sign in to Govforms through the connection flow.
- Select the libraries needed for the task.
- Choose form-design access and Response Hub data access separately for each library.
- Review the discovered tools and begin with an inspection task to confirm the connection.
No library access is selected by default. The connection grant and your current library role are checked on each call. If your role changes, the connection follows the new permissions.
Choose access for each area
| Grant | Form designs | Response Hub data |
|---|---|---|
| No access | The client cannot inspect service designs. | The client cannot inspect collections, respondents or submissions. |
| Read-only | Inspect designs and deployment status. | Inspect authorised operational data, responses and review history. |
| Full access | Make permitted design changes and prepare deployments. | Perform permitted collection, assignment and review operations. |
The areas are independent. You can let a client improve a service design without exposing live respondent data, or give an operational client the Response Hub access needed for its workflow. Full access remains limited by your role and the operation's requirements.
What clients can do
Depending on the connection and available tools, clients can find libraries, services and patterns; inspect service structure; create and update designs; read deployment information; and prepare publication steps. Guidance resources describe the platform model, field types, Liquid and supported integrations.
With separate Response Hub permission, clients can inspect authorised submissions and reviews, manage collection configuration and assignments, or perform supported review actions. Additional design or deployment permissions apply where an operation also changes or publishes a collection form.
A publication preparation result or browser approval link is not a completed deployment. Complete the required human step and check the returned status. Submitted Response Hub versions and audit records remain protected from rewriting.
Use API-key MCP for server integrations
For a controlled server-side connection, use the library-scoped endpoint:
https://govforms.uk/builder/libraries/{libraryId}/mcpAPI-key permissions separately govern form reads, writes, deployments and Response Hub access. The key's tool catalogue includes only permitted operations. Keep the key on the server and use the authentication requirements documented for the endpoint.
Plan usage and review changes
MCP tool calls use API units according to the operation they run. Read the Govforms MCP capabilities reference for unit tiers, transport details and the wider tool coverage.
For a design task, give the client a clear brief and inspect its changes in Builder and User view. For an operational workflow, choose the precise library, data area and permissions it needs, and review actions that affect respondents or published services.
See Govforms API for direct integrations and Response Hub API for operational data access.