Integration

Basin integration

Basin is a no-code form backend. Read, search and triage form submissions (mark read, spam or trash, delete), re-send submissions to a form's webhooks, create and configure forms and projects, manage HTML mail templates, and read or delete form webhooks and legacy Form Builder views. API access needs the Growth, Pro or Agency plan. Authentication is an Account API key (all forms) or a Form API key (one form) sent as Authorization: Token <key>. Submitter IP addresses, user agents and attachments, form recipient addresses, CAPTCHA secrets and webhook URLs are not returned; creating or changing webhooks, redirect and reply-to addresses stay in the dashboard. The list routes for forms, projects, domains, webhooks and form views are not exposed (their answer format is undocumented), so take ids from the dashboard or from get_form.

Connect Basin How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Basin.Built from the 22 Basin tools below, on the connection you add once.

What you can do with Basin

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Mail template, 5 operations

create_mail_templateCreate mail templatePOSTCreates a mail template (HTML email layout) in a project. Its HTML goes through Basin's approval: body returns the latest submitted HTML until it is approved.
delete_mail_templateDelete mail templateDELETEDeletes a mail template for real. Answers with no content.
get_mail_templateGet mail templateGETReturns one mail template by id (from list_mail_templates): name, project and HTML body.
list_mail_templatesList mail templatesGETLists the mail templates of one project (project_id required), with paging meta. Use a template id as a form's notification, auto-response or confirmation template.
update_mail_templateUpdate mail templatePUTChanges a mail template's name or HTML for real (last write wins). Only the fields you send change; new HTML goes through Basin's approval before it is used.

Form, 4 operations

create_formCreate formPOSTCreates a form for real under a project you own or administer; returns it with its endpoint id (uuid). With autoreply true, Basin emails every new submitter. Form Studio fields cannot be created by API.
delete_formDelete formDELETEDeletes a form for real. Returns the deleted form's settings (recipient addresses and secrets not returned).
get_formGet formGETReturns one form's settings by id: name, project, timezone, spam protection, autoreply and notification texts, mail templates, branding, retention and submission counts. Recipient addresses and secrets are not returned.
update_formUpdate formPUTChanges a form's settings for real. Only the fields you send change. Setting autoreply true makes Basin email every new submitter. Redirect URLs, reply-to and CAPTCHA secrets stay in the dashboard.

Project, 4 operations

create_projectCreate projectPOSTCreates a project (a folder of forms and mail templates) and returns it with its id.
delete_projectDelete projectDELETEDeletes a project for real and returns it.
get_projectGet projectGETReturns one project by id: its name and dates. Project ids appear as project_id on forms and mail templates.
update_projectUpdate projectPUTRenames a project for real and returns it.

Submission, 4 operations

delete_submissionDelete submissionDELETEDeletes a submission for real (answers 422 when it could not be deleted). To keep it recoverable, move it to the trash with update_submission instead.
get_submissionGet submissionGETReturns one submission by id (from list_submissions): every field the submitter sent, its email, spam, read and trash status and dates. IP address, user agent and attachments are not returned.
list_submissionsList submissionsGETLists form submissions, up to 100 per page. Filter by form, status (new, spam, trash, all), search text or date range; page with page. A Form API key always returns its own form only.
update_submissionUpdate submissionPATCHChanges a submission's status for real: mark it read or unread, flag or unflag it as spam, or move it to or out of the trash. Only the fields you send change.

Form webhook, 2 operations

delete_form_webhookDelete form webhookDELETEDeletes a form webhook for real: new submissions stop being sent to it. Returns the deleted webhook (destination URL not returned).
get_form_webhookGet form webhookGETReturns one form webhook by id: its name, form, payload format, whether it is enabled and also fires for spam, and its failure count. The destination URL is not returned.

Submission webhook, 2 operations

refire_submissions_webhooksRefire submissions webhooksPOSTRe-sends several submissions to every enabled webhook of their forms, for real: their data is posted again (queued at once). With a Form API key only that form's submissions are re-sent.
refire_submission_webhooksRefire submission webhooksPOSTRe-sends one submission to every enabled webhook of its form, for real: its data is posted again to those services (queued at once). With a Form API key the submission must belong to that form (else 403).

Form view, 1 operation

get_form_viewGet form viewGETReturns one legacy Form Builder (Form.io) view by id: its form schema, embed code, styling, iframe settings, opening and closing dates, and the form and project it belongs to. Form Studio forms are not available through the API.

Use Basin from Claude Code, Cursor or Codex

Connect Basin in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Basin operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Basin

Create your workspace
Sign up free. Nothing to install.
Connect Basin once
Add your Basin connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.