LanesLanes
Use cases/Lanes Forms/Let your AI agent provision a form

Let your AI agent provision a form

Your coding agent can create a live form endpoint mid-task over MCP, with no signup, and hand you a link to claim it.

When an agent is building your site, the form should not be a detour. With the Lanes MCP server, the agent provisions a working form endpoint itself, mid-task, and hands you a link to claim it.

The server is hosted at api.lanes.sh/mcp over streamable HTTP, so there is nothing to install and nothing to run locally. It registers under the name lanes, separate from the desktop app's Lanes Desktop MCP server, and creating or submitting to forms needs no key at all. All three Lanes MCP servers and when to use each are covered in MCP.

How it works

  • Add the MCP server. claude mcp add --transport http lanes https://api.lanes.sh/mcp, no signup. Other MCP clients point at the same URL with the equivalent JSON config.
  • The agent calls create_form. One tool call returns a live endpoint and a claim link. The server exposes five tools: create_form, get_form, update_form, generate_form_snippet, and submit_form. Creating and submitting work anonymously; the management tools need a workspace key. See agents and MCP.
  • The form works immediately. Submissions are captured from the first second. While unclaimed, the form holds up to 25 submissions and forwards nothing, which fits a form born mid-task: the data waits until a human takes over. Limits are in provisioning.
  • You claim it. Follow the claim link to pull the form into your dashboard when you are ready. Possession of the link is the authorization, so the agent can provision on your behalf and you still end up as the owner. Claiming releases the held submissions and turns on email forwarding. See claiming.

Why it matters

The agent stays in flow. No dashboard detour, no API keys to paste, no backend to write. The form is live before the agent moves to the next task.

The markup is covered too: generate_form_snippet emits a ready-to-paste HTML or React form wired to the endpoint, so the agent does not hand-write the integration. And if you already have a workspace, pass your lfk_ key as an Authorization bearer header: management tools unlock, and new forms are born claimed into that workspace with no claim step at all.

MCP is not the only path. The lanes-forms Claude Code skill carries the API contract (/plugin marketplace add lanes-sh/app, then /plugin install lanes-forms@lanes), and a plain copy-paste prompt works for any agent. Every docs page is also readable as raw Markdown at its own path with a /raw suffix, so agents can ground themselves without scraping.

Set it up

  1. Connect the server. Run claude mcp add --transport http lanes https://api.lanes.sh/mcp in your agent, or add the equivalent server entry to its MCP config.
  2. Ask for a form. Tell the agent what the form should collect and which address should receive submissions. It calls create_form and reads back the endpoint and the claim link.
  3. Let it wire the page. Ask for generate_form_snippet output and the agent pastes a working HTML or React form into your site.
  4. Claim the form. Open the claim link the agent hands you, sign in, and the form joins your dashboard with everything it collected.
Without this, the agent's run breaks in the middle: it stops, you open a dashboard, sign up, create the form by hand, then paste ids and keys back into the session. An anonymous create over MCP removes the human hop, and the claim link moves ownership to you afterwards instead of blocking the work up front.

Further reading

Read agents and MCP or see Lanes Forms.