The FormsByAir connector lets Claude work in your FormsByAir account. Claude signs in with your FormsByAir login; nothing is installed and there are no keys to manage. It pairs with the form-authoring skill, which teaches Claude how FormsByAir forms are built.

What Claude can do

With the connector connected and the skill installed, Claude can:

• list the forms in your account and their version history
• download a form’s schema, make changes, and upload it as a new version of a Draft or Test form
• download and upload integration maps and delivery templates
• create a Test copy of a production form, and deploy a Test form onto production after sign off

It cannot read submitted documents, publish or unpublish forms, or change account settings.

Production forms

Production forms are never changed directly. Claude follows the same release path you would: changes are made on a Test form, tested there, and deployed onto the production form as a new version with a comment in the form’s version history. The deploy refuses if the production form has changed since it was reviewed. Rolling back is the portal’s revert-to-version.

By default a deploy carries the schema only. Maps and templates are carried across only when you ask, and Claude shows you what would be overwritten first, so a map or template that was only ever meant for testing never reaches production by accident.

Who can connect

The connector is available to Administrators of a FormsByAir account. Anyone else who tries to connect is told so on the sign-in page. Claude acts as you, in the account your login is in, and everything it does is recorded against you the same way as if you’d done it in the portal.

Partners work across their client accounts the same way they do in the portal: ask Claude to list your accounts and switch to the one you want to work in. Switching is the same setting your portal session uses, so it moves your portal too. Claude confirms the current account before it changes anything.

It works in Claude Desktop, claude.ai on the web, the Claude mobile apps, and Claude Code.

Connect

Claude Desktop or claude.ai

1. Open Customize in the sidebar (Settings on the web), then Connectors.
2. Click +, then Add custom connector.
3. Enter the name FormsByAir and the URL https://formsbyair.com/mcp, then click Add.
4. Click Connect. Your browser opens the FormsByAir login (skipped if you’re already signed in) and then a page asking you to allow Claude to connect to your account. Click Allow.

The connection then works on every Claude surface you’re signed in to.

Claude Code

In a terminal, run

claude mcp add --transport http --scope user formsbyair https://formsbyair.com/mcp

then start claude, type /mcp, choose formsbyair and Authenticate to go through the same login and consent.

Team and Enterprise organisations

An organisation owner adds the connector once under Organization settings → Connectors → Add → Custom → Web, with the same URL. Members then just click Connect under Customize → Connectors and sign in themselves.

Install the skill

Claude will tell you if the skill is missing or out of date the first time you use the connector, and offer to install it. In Claude Code it does the install itself; in Claude Desktop and claude.ai it gives you the download link and the upload steps. See Skill for the download and the manual steps.

First steps

In a chat with the FormsByAir connector enabled (the + button, then Connectors), ask:

Which FormsByAir account am I in, and which forms do I have?

Claude confirms the account before doing anything, and the first time it uses a tool it asks your permission. Allow the read tools freely; keep the upload and deploy tools on ask, so every change to a form is one you’ve seen.

A good first job: pick a Test form and ask Claude to add a question to it. A good second job: ask it to explain how a form’s integration map works.

Disconnecting

In Claude Desktop or claude.ai, remove the connector under Customize → Connectors. In Claude Code, run claude mcp logout formsbyair or choose Clear authentication in /mcp. Access tokens expire within an hour of disconnecting.