Basin MCP server for AI agents

Live

API KEY

FORM BACKEND

Developer Tools

Basin gives your agent form backend access: list and read form submissions, mark them read, spam, or trashed, create and update forms with notifications, autoreplies, and spam protection, and manage projects and email templates.

  • Per-user credentials: each call uses the actual user's API key, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Basin
agent · Acme Q3
Run
Any new submissions on the Contact Sales form today?
S
basin_list_submissions
97ms
Forms agent
5 new submissions came in today. 2 are from companies over 500 employees asking for a demo, and 1 looks like spam.
Sources: Contact Sales form, 5 submissions
basin
5 submissions
18:29
Message Claude...

Tools your forms agent reaches for on Basin, scoped per user.

CALL ANY TOOL
20 tools for your form backend in Basin: list, read, and triage form submissions, create and update forms, manage projects and HTML email templates, and list custom sending domains.
basin_create_form
Create form
Create a new form in a Basin project, with optional notification, autoreply, and spam protection settings. Returns the form record: id, uuid, name, project_id and project_name, timezone, redirect_url, notification and autoreply settings, spam protection flags, retention_days, form_webhooks, and inbox, spam and trash counts. The uuid is the form's endpoint ID (https://usebasin.com/f/<uuid>). Use basin_update_form to change an existing form. Form Studio fields cannot be added through the API; build them in the Basin dashboard.
Parameters
Name
Type
Required
Description
name
string
Required
Name of the form as shown in the Basin dashboard. Example: Contact form.
additional_settings
object
Optional
Any other form attribute from Basin's API reference, as a JSON object merged into the form. Use it for settings that have no input above, such as redirect page text and colors (redirect_heading, redirect_message, button_background_color), mail templates (notification_mail_template_id, auto_response_mail_template_id), a custom sending domain (domain_id, domain_email), or use_ajax. Inputs above win over the same key here. Example: {"redirect_heading": "Thanks!", "button_background_color": "#24292E"}.
allowed_domains
array
Optional
List of website domains allowed to submit to this form. Sending a list replaces the current one. Example: ["example.com", "www.example.com"].
autoreply
boolean
Optional
Set true to send an automatic reply email to the person who submitted the form, false to turn it off. Example: true.
autoreply_body
string
Optional
Body text of the automatic reply sent to the submitter. Example: We received your message and will reply within one business day.
autoreply_from_name
string
Optional
Sender name shown on the automatic reply. Example: Acme Support.
autoreply_subject
string
Optional
Subject line of the automatic reply sent to the submitter. Example: Thanks for contacting us.
blocked_domains
array
Optional
List of domains whose submissions are blocked. Sending a list replaces the current one. Example: ["spam-domain.test"].
content_blacklist
array
Optional
List of words or phrases that mark a submission as spam when they appear in it. Sending a list replaces the current one. Example: ["casino", "crypto giveaway"].
duplicate_filter
boolean
Optional
Set true to filter out duplicate submissions, false to accept them. Example: true.
force_hcaptcha
boolean
Optional
Set true to require hCaptcha on submissions to this form. Example: false.
force_recaptcha
boolean
Optional
Set true to require Google reCAPTCHA on submissions to this form. Example: false.
honeypot_field
string
Optional
Name of a hidden honeypot input in your HTML form. Submissions that fill it in are treated as spam. Example: _gotcha.
notification_bcc_emails
string
Optional
Comma-separated list of 'bcc' recipients for notification emails. Sending a list replaces the current bcc recipients; leave out to keep them. New addresses must be verified. Example: archive@example.com.
notification_cc_emails
string
Optional
Comma-separated list of 'cc' recipients for notification emails. Sending a list replaces the current cc recipients; leave out to keep them. New addresses must be verified. Example: manager@example.com.
notification_emails
string
Optional
Comma-separated list of 'to' recipients for new-submission notification emails. Sending a list replaces the current recipients; leave out to keep them. Newly added addresses must be verified before they receive notifications. To remove all recipients, send {"notification_emails": ""} in additional_settings. Example: sales@example.com,ops@example.com.
notification_from_name
string
Optional
Sender name shown on notification emails. Example: Website Forms.
notification_subject
string
Optional
Subject line of the notification email sent for each new submission. Example: New website lead.
project_id
integer
Optional
ID of the project the form belongs to. Use the id field returned by basin_list_projects. Example: 1024.
redirect_url
string
Optional
URL Basin redirects the visitor to after a successful submission. Example: https://example.com/thanks.
retention_days
integer
Optional
Number of days Basin keeps submissions for this form before deleting them. Example: 90.
smtp_email_validation
boolean
Optional
Set true to check submitted email addresses against their mail server before accepting the submission. Example: true.
timezone
string
Optional
Time zone used for the form's dates and date-range filters, as Basin stores it (for example the zone name shown in the form settings). Example: Eastern Time (US & Canada).
basin_create_mail_template
Create mail template
basin_create_project
Create project
basin_delete_form
Delete form
basin_delete_mail_template
Delete mail template
basin_delete_project
Delete project
basin_delete_submission
Delete submission
basin_get_form
Get form
basin_get_mail_template
Get mail template
basin_get_project
Get project
basin_get_submission
Get submission
basin_list_domains
List domains
basin_list_forms
List forms
basin_list_mail_templates
List mail templates
basin_list_projects
List projects
basin_list_submissions
List submissions
basin_update_form
Update form
basin_update_mail_template
Update mail template
basin_update_project
Update project
basin_update_submission
Update submission
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Basin tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["basin"], toolNames: [
    "basin_list_forms",
    "basin_list_submissions",
    "basin_update_submission"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Triage today's Contact Sales submissions and mark spam" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["basin"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Triage today's Contact Sales submissions and mark spam" }],
  tools,
});

// Execute the tool call with the user's vaulted Basin API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["basin"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Triage today's Contact Sales submissions and mark spam" }],
  tools,
});

// Tool call runs with the user's vaulted Basin API key
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["basin"] }, pageSize: 100,
});

const agent = new Agent({
  name: "forms_agent",
  model: "gemini-2.5-pro",
  instruction: "Basin tools scoped to this user",
  tools,
});

await agent.run("Triage today's Contact Sales submissions and mark spam");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Basin tool. Click to copy, paste into your agent, done.
Submissions
Copy the prompt
Copied
List unread submissions on the Contact Sales form from today.
Copy the prompt
Copied
Show the full payload of the latest Careers form submission.
Copy the prompt
Copied
Mark every submission from this week that mentions crypto offers as spam.
Forms
Copy the prompt
Copied
Create a Beta Waitlist form in the Website project with an autoreply.
Copy the prompt
Copied
List every form in the Marketing project.
Copy the prompt
Copied
Change the notification email on the Contact Sales form to sales@acme.com.
Projects and templates
Copy the prompt
Copied
Create a project called Product Launch.
Copy the prompt
Copied
List the email templates in the Website project.
Copy the prompt
Copied
Update the Thanks for reaching out template with our new support hours.
SEE HOW AUTH WORKS
Each user connects their own Basin API key once, and Scalekit sends it with every call. API keys stay vaulted, every call is scope checked, and every action is logged.
1
Authorize
Your user connects
Basin
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Basin
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Basin
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Basin
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other developer connectors.
GTM and RevOps Teams
CRM AI agent
Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.
Support and Ops Teams
Support ticket automation agent
Fetches new Zendesk tickets, drafts a reply from Notion knowledge base articles, digests what it cannot answer to Slack, and archives the rest, acting as the support agent rather than a shared API key.
Test other agents
See the same per-user auth pattern across other developer connectors.
GTM
CRM AI agent
Turn each Granola call transcript into a HubSpot record update, a drafted Gmail follow-up, and a Slack recap.
SUPPORT
Support ticket automation (Google ADK)
Fetch, annotate, and archive Zendesk tickets with Notion context, digesting anything it cannot answer to Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared Basin API key looks fine in a demo. In production every submission update and form change looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Basin today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Basin as the user or through a shared API key?
As the user. Each user connects their own Basin API key once, and Scalekit sends it with every call. Audit logs attribute every submission update and form change to that user, not a shared service account.
Where is the Basin API key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.
Can I limit what the agent does in Basin?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example the submission read tools and basin_update_submission without basin_delete_form or basin_delete_submission, which permanently delete data. Scalekit also enforces scope checks before every API call.
What happens when a user revokes Basin access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Which Basin is this connector for?
Basin, the form backend at usebasin.com. The tools work with the projects, forms, submissions, email templates, and sending domains in the user's Basin account.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""basin"": {
""url"": ""https://mcp.scalekit.com/basin"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.basin]
url = ""https://mcp.scalekit.com/basin""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""basin"": {
""url"": ""https://mcp.scalekit.com/basin"",
""type"": ""http""
}
}
}