Cube Forms: What It Is, What It Costs and Who It’s For

Cube Forms: What It Is, What It Costs and Who It’s For

⚠️ Affiliate Disclosure: This post is not an affiliate associated review. It may become one in the future and this disclosure will reflect that. This does not affect my reviews and I only recommend tools I genuinely believe in.

Cube Forms launched on Product Hunt on 12 October 2026 as “forms that can be filled by agents”. I haven’t tested Cube Forms — this is an information guide for developers weighing it up, not a review. Maker Bonan Kou pitches it as an early piece of an “agent-friendly internet”: the same form works for a person in a browser and for an AI agent over MCP or plain HTTP, and the maker describes it on Product Hunt as free and early.

Cube Forms logo — AI dev tool guide on WhatAITools

What Is Cube Forms and What Does It Do?

Cube Forms is a form builder where every form has two front doors. People fill the form in the browser as usual. Agents — Claude Code, ChatGPT, Cursor, or anything that speaks MCP or HTTP — can read the same form as structured data, fill it in without opening the page, and hand the person a link to review and submit. The homepage demo shows an agent completing a six-answer bug report and asking its user to check the answers before sending. Templates on the site include bug reports, event registration, talk-to-sales, feedback, client intake and job applications.

How Does Cube Forms Work?

The docs describe two MCP servers. A public one at ui.usecube.io/mcp needs no sign-in and exposes tools such as list_forms, read_form, submit_form, prefill_link and draft_form. An owner server at /mcp/owner uses OAuth 2.1 with PKCE and adds form management — create_form, list_answers, export_answers, update_form and so on. In Claude Code, setup is one line: claude mcp add --transport http cube https://ui.usecube.io/mcp.

There’s a plain HTTP layer too. GET /f/<id> returns the form as Markdown (or .json for the JSON Schema), and POST /f/<id> with an answers object submits it — 201 on success, 400 with an errors list on a mistake, rate-limited to ten submissions a minute per address. Files go up as multipart, base64 or a URL the server fetches, capped at 10MB per file and 50MB per submission. Owner routes behind a bearer token cover CSV export, file retrieval and answer deletion.

How Much Does Cube Forms Cost?

Neither the homepage nor the docs publish any pricing (checked 13 Oct 2026). The only call to action is “Create for free”, and the maker calls the product “free and early” on Product Hunt. There is no published paid tier, no stated limits on forms or responses beyond the rate and file caps above, and no indication of what a paid plan might cost later.

PlanDetails
FreeCurrently the only option — “Create for free”; maker calls it “free and early”
Paid plansNone published as of 13 Oct 2026
Usage caps stated10 submissions/minute per address; 10MB per file; 50MB per submission

What Are Developers Saying About Cube Forms?

I searched for independent developer feedback on 13 Oct 2026 and found nothing — Cube Forms launched a day earlier and is too new for meaningful feedback. Everything here comes from the vendor’s own pages and the Product Hunt listing.

Who Is Cube Forms For?

Cube Forms makes most sense for developers already working agent-first — people running Claude Code or Cursor who want intake forms, bug reports or sign-ups their agent can file without screen-scraping a Typeform. The clean JSON Schema and Markdown representations also make it a tidy test bed for anyone experimenting with agent-to-service workflows over MCP. If you just need a conventional form builder, established names like Typeform, Tally or Google Forms have the track record Cube Forms can’t yet show — though none of those documents an agent-native interface like this. I haven’t compared them hands-on.

Cube Forms: Pros & Cons On Paper

Pros

  • Cube Forms documents both MCP and plain HTTP access, so agents without MCP support aren’t locked out
  • Cube Forms is currently free, with no card or sign-in needed for the public MCP server
  • Proper OAuth 2.1 with PKCE on the owner server — more careful auth than many young MCP tools document
  • Human review built into the flow: the agent fills, the person checks the link before submitting

Cons

  • Cube Forms publishes no pricing or paid roadmap, so long-term costs and limits are unknowable today
  • Cube Forms names no company behind it — a single-maker project carries continuity risk for anything business-critical
  • Cube Forms is too new to have any independent feedback I could find
  • All capability claims are documentation, not tested behaviour — untested here

Is Cube Forms Worth a Look?

For a developer curious about agent-native services, yes — Cube Forms costs nothing to try, the MCP setup is one command, and the HTTP API is simple enough to poke at with curl in five minutes. For anything you’d rely on, the missing pricing and anonymous ownership are real question marks. This is not a scored verdict: I haven’t tested it, and whether the agent-filling flow works as smoothly as the demo suggests is exactly the kind of thing only hands-on use can answer.

Used Cube Forms? Tell Me How You Find It

I don’t test developer tools — you’re the expert here. If you’re using Cube Forms, leave a comment: what works, what doesn’t, and what you’d choose instead. Honest developer experience is worth more than anything I can write from the vendor’s pages, and it helps the next dev weighing it up.


Tried this tool?

Share your experience below — your review helps other everyday people make better decisions.

Leave a Reply

Your email address will not be published. Required fields are marked *