formly
Registry code: 06ca252ee616680d
Use these tools to create workspaces and create, edit, publish, and read Formly forms for the authenticated user. To build a form, call create_form with a plain-language description - Formly's AI designs the structure. If the user asks for a new workspace, call create_space first and pass the returned spaceId to create_form.
- endpoint
- https://api.formly.so/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is formly live?
- Yes — it answered the hub's last check (checked 7h ago). It answered 99% of checks over the last 30 days.
- Is formly free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does formly have?
- 10 tools: create_form, publish_form, create_space, update_form_settings, get_form, unpublish_form, edit_form, list_forms, ….
- Is formly safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.2%· all time 99.2%
last good check
of 10 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- productivity & business
- used for
- create a form from a description
- edit a form
- publish a form
- get form submissions
- takes → gives
- text → data
- tools
- 4 reads6 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
create_form changes data auth-required never probed
Create a brand new form from a natural-language description. Formly's own AI designs the full form (pages, questions, field types) - you do NOT need to specify field structure. Returns the new form id and an editable + public URL. Optionally publish it immediately. IMPORTANT: if the user has more than one workspace and you don't pass spaceId, this returns the list of workspaces - ask the user which one to use, then call again with that spaceId.
{ "type": "object", "required": [ "description" ], "properties": { "name": { "type": "string", "description": "Optional explicit form title." }, "publish": { "type": "boolean", "description": "Publish the form immediately so it is live. Default false." }, "spaceId": { "type": "string", "description": "Workspace id to create the form in. If omitted: used automatically when the user has exactly one workspace; if they have several, the call asks you to pick one (call list_spaces and ask the user)." }, "multiPage": { "type": "boolean", "description": "Split the form across multiple pages. Default true." }, "description": { "type": "string", "description": "What the form is for, in plain language. E.g. 'a customer feedback survey with a rating and an open comment'." }, "personalized": { "type": "boolean", "description": "Use answer piping so later questions reference earlier answers. Default false." } }, "additionalProperties": false }arguments 33 linespublish_form changes data auth-required never probed
Publish a form so it becomes live and can accept responses (uses the current draft).
{ "type": "object", "required": [ "formId" ], "properties": { "formId": { "type": "string", "description": "The form id (shortId)." } }, "additionalProperties": false }arguments 13 linescreate_space changes data auth-required never probed
Create a new Formly workspace (space) for the user and return its spaceId. Use this before create_form when the user asks to create a new workspace and place a form inside it.
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "description": "Workspace name." }, "description": { "type": "string", "description": "Optional workspace description." } }, "additionalProperties": false }arguments 17 linesupdate_form_settings changes data auth-required never probed
Update a form's settings (the dashboard Settings tab): redirect after submit, progress bar, partial submissions, remove Formly branding, email notifications, SEO title/description, password protection, duplicate prevention, and language. Only the keys you pass change. Note: image uploads (ogImage, logo) are not supported here - those need the dashboard.
{ "type": "object", "required": [ "formId", "settings" ], "properties": { "formId": { "type": "string", "description": "The form id (shortId)." }, "settings": { "type": "object", "properties": { "language": { "type": "string", "description": "Language code, e.g. 'en'." }, "password": { "type": "string", "description": "Password (required if passwordProtected is true)." }, "redirect": { "type": "boolean", "description": "Redirect to a URL after submit." }, "seoTitle": { "type": "string" }, "progressBar": { "type": "boolean", "description": "Show a progress bar." }, "redirectUrl": { "type": "string", "description": "Redirect target (required if redirect is true)." }, "formlyBranding": { "type": "boolean", "description": "Show Formly branding (false removes it)." }, "seoDescription": { "type": "string" }, "selfEmailReplyTo": { "type": "string" }, "selfEmailSubject": { "type": "string" }, "passwordProtected": { "type": "boolean", "description": "Require a password to open the form." }, "preventDuplicates": { "type": "boolean", "description": "Prevent duplicate submissions." }, "selfEmailFromName": { "type": "string" }, "partialSubmissions": { "type": "boolean", "description": "Save partial submissions." }, "preventDuplicatesBy": { "type": "string", "description": "How duplicates are detected, e.g. 'ip'." }, "respondentEmailContent": { "type": "string" }, "respondentEmailReplyTo": { "type": "string" }, "respondentEmailSubject": { "type": "string" }, "selfEmailNotifications": { "type": "boolean", "description": "Email you on each submission." }, "respondentEmailFromName": { "type": "string" }, "respondentEmailNotifications": { "type": "boolean", "description": "Email the respondent after they submit." } }, "description": "Partial settings to merge - only provided keys change.", "additionalProperties": false } }, "additionalProperties": false }arguments 96 linesget_form reads auth-required 15h ago
Get a single form's full structure (pages and blocks), settings, and URLs by its id.
{ "type": "object", "required": [ "formId" ], "properties": { "formId": { "type": "string", "description": "The form id (shortId)." } }, "additionalProperties": false }arguments 13 linesunpublish_form changes data auth-required never probed
Unpublish a form so it is no longer live.
{ "type": "object", "required": [ "formId" ], "properties": { "formId": { "type": "string", "description": "The form id (shortId)." } }, "additionalProperties": false }arguments 13 linesedit_form changes data auth-required never probed
Edit an existing form's CONTENT using a natural-language instruction (e.g. 'add a phone number field', 'make the email optional', 'add a thank you page'). Formly's AI figures out and applies the changes. If the form is already published, the live version is updated too. NOTE: this only changes questions/fields/pages/headings - for settings like branding, redirects, email notifications, SEO, or password protection, use update_form_settings instead.
{ "type": "object", "required": [ "formId", "instruction" ], "properties": { "formId": { "type": "string", "description": "The form id (shortId)." }, "instruction": { "type": "string", "description": "What to change, in plain language." } }, "additionalProperties": false }arguments 18 lineslist_forms reads auth-required 15h ago
List the user's forms, optionally filtered by workspace. Returns each form's id, name, published status, and URLs.
{ "type": "object", "properties": { "spaceId": { "type": "string", "description": "Optional workspace id to filter by." } }, "additionalProperties": false }arguments 10 lineslist_spaces reads auth-required 15h ago
List the Formly workspaces (spaces) the user can access. Use this to find a spaceId before creating a form in a specific workspace.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_submissions reads auth-required 7h ago
Get recent responses (submissions) for a form, newest first. Returns the answer data for each submission.
{ "type": "object", "required": [ "formId" ], "properties": { "limit": { "type": "number", "description": "Max submissions to return (1-200). Default 50." }, "formId": { "type": "string", "description": "The form id (shortId)." } }, "additionalProperties": false }arguments 17 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id06ca252ee616680d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/06ca252ee616680d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/06ca252ee616680d?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.