Create a temporary demo with an AI client

Ask an AI client to build a working Govform demo that you can try and share in a browser, without creating an account. Each demo lasts 14 days. Use sample information only: demos are demonstrations, not real services.

Connect your AI client

Add https://govforms.uk/builder/try/mcp as an HTTP MCP server. This separate connection needs no sign-in or API key. It supports JSON-RPC POST requests with Content-Type: application/json; GET and batch requests are not supported. It is available when the demo connection has been enabled on the Builder you use.

After connecting, ask the client to read govform-demo://docs/guide and discover the tools. Model guidance is also available at govforms://docs/model. Use getGovformsModelDocumentation and getFormExamples when the connection advertises them.

Create, try and change a demo

1. Describe the service and the routes you want people to try. The AI uses create_demo_service with a complete form definition and optional settings.
2. Before handing the demo back, the AI should open the returned prototypeUrl using browser tools, inspect layout, styling, branding and text at desktop and mobile widths, and try the main journey with sample information to check navigation and validation. It should fix issues and recheck after changes. If browser tools are unavailable or access is blocked, it should tell you that visual verification was not completed. Complete any human verification shown before the service starts. Share this URL with people who will try the demo.
3. Keep the returned managementToken private. It is needed to read, change or delete the demo and cannot be recovered. Never include it in the shared link.
4. For later changes, read the demo first and use its latest ssId as expectedSsId. Govform checks that revision while holding the form lock. If another save completed first, your change is rejected; read the latest definition and reconstruct the edit before retrying.

Tool	What it does
create_demo_service	Accepts form, optional formName and optional settings. Returns the demo ID, URL, expiry, revision and one-time management token.
get_demo_service	Reads the definition and settings using demoId and managementToken.
replace_demo_service	Replaces the full definition, preserving settings and expiry. Also requires expectedSsId.
update_demo_settings	Replaces the whole settings object. Omitted settings return to defaults. Also requires expectedSsId.
delete_demo_service	Permanently removes the demo and its answers and history.

All tools after creation require the demo ID and management token. A missing demo, expired demo or wrong token returns the same not-found tool error. Allowed Darcy editing tools also work on that one demo: supply its identity and token, with the latest revision for changes. Documentation and Liquid preview tools need no demo identity. Use only the tools and arguments advertised by the connection.

Make it your own

Set the header, logo, footer, colours, layout and region for the individual demo. Font choices are Outfit and Roboto. Images can be PNG, JPEG, GIF or WebP data URLs, up to 256 KB each. Region settings are defaultCountryCode, defaultLocale, defaultTimeZone and defaultCurrency. The tools advertise the complete accepted settings schema.

Custom CSS or Sass, free-text fonts, custom font URLs and GOV.UK branding are unavailable. Every page keeps the Govform demo banner and a title beginning “Govform demo”. Links to other websites are replaced with “[External link redacted]”, and external redirects are stopped.

What you can demonstrate

Build questions, content, conditions, calculations, repeated groups and internal routes using the allowed types in the demo guide. API, email and AI actions are simulated in User view. Demos cannot accept file uploads, read another service’s data, use library connections or secrets, take payments, generate PDFs, use custom domains or deploy as live services. The connection cannot list other people’s demos.

Limits and expiry

A definition can contain up to 50 pages and 512 KB. Each address can create 10 demos per hour and make 60 MCP requests per minute. The platform limit is 1,000 active demos, checked before creation. Limits return HTTP 429 with Retry-After. Most definition, token and revision errors use the ordinary MCP tool-error response.

A demo expires 14 days after creation. Visits and edits do not extend it. Expired demos return not found and are permanently removed by scheduled cleanup. To continue, create another demo using your saved definition.

For authenticated work on your own libraries, see Connect AI clients with Govform MCP. Saving a demo does not create an account, grant Builder access or deploy anything.