Use NeetoForm in Claude Code

Check requirements

• Claude Code installed on your computer.
• A NeetoForm account.

Connect NeetoForm to Claude Code

claude mcp add --transport http --scope user neetoform \
  https://connect.neetoform.com/mcp/messages

Start Claude Code, run /mcp, select neetoform, and sign in to your NeetoForm account.

Connect with an API key

An API key is not tied to a person. Every tool call reaches the whole workspace, and role checks do not run. Use one for automation that must see every form. Do not use one on a machine where the person should see only their own forms.

Get a key at help.neetoform.com/articles/api-keys. It is the same key the REST API uses. Send it in this header:

Authorization: Bearer YOUR_API_KEY

Add the server to ~/.claude.json, then restart Claude Code:

{
  "mcpServers": {
    "neetoform": {
      "type": "http",
      "url": "https://connect.neetoform.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Let Claude Code use the CLI

You don't have to write these scripts yourself. Claude Code, Codex, or another coding agent can write the automation and use the open-source NeetoForm CLI to work with your account. Run neetoform setup claude (or setup codex, setup cursor) once, then ask:

Every Monday at 8 AM, use the NeetoForm CLI to export last week's Lifeline Run registration submissions to CSV and email it to the race team. Write the script, test it, and set up the cron job.

Using the NeetoForm CLI, write a script that saves every submission from all our active forms as JSON, one file per form.

You get the convenience of a chat, and the result is a script you can read, run, and commit.

Try these prompts

Your AI assistant can also build and manage forms when you grant the Create and update permission.

Build a form

Create a NeetoForm form called Event registration with fields for full name, email, company and a dropdown for the session they want to attend.

The assistant creates a draft. Nothing is live until you publish.

Start a new form from the NeetoForm job application template.

On the Event registration form, make the company question optional and show the dietary needs question only when someone picks the dinner session.

After someone registers, email them a confirmation and send the details to events@example.com.

Preview, publish, and share

Show me what the Event registration form looks like before I publish it.

In clients that support MCP Apps, such as Claude, the form appears inside the chat. Other clients get a link that opens the preview in your browser.

Publish the Event registration form and give me its link and an embed code for our website.

Close the Event registration form after 200 submissions or on 30 November, whichever comes first.

Email an invitation to fill in the Event registration form to oliver@example.com and sam@example.com.

The emails go to real people, so check the addresses and the message before the assistant sends them.

Read and export results

Across the last 50 submissions to Customer feedback, how did people answer the recommendation question?

How is the Event registration form doing this month?

The assistant reads the form's insights: visits, starts, completed submissions, completion rate, and the devices people used.

Export every submission to the Event registration form to Excel and email it to me.

The file is built in the background, and a download link is emailed to you.

Combine with other context

Take the emails from this week's Event registration submissions and draft a follow-up message for each one.

More team prompts

Who is in my NeetoForm workspace, and what role does each of them have?

Set Oliver Smith's time zone to America/New_York in NeetoForm.

Troubleshooting

Your AI assistant shows no NeetoForm tools

Restart the client first. Every client reads its MCP config at startup. On Claude or ChatGPT, confirm that you added the connector and finished the sign-in. In ChatGPT, the plugin is created only after you tick I understand and want to continue.

On a client that reads a config file, check these:

1. The config key. Claude Code, Cursor, Devin, Antigravity, and Antigravity CLI use mcpServers. VS Code uses servers. Codex uses a [mcp_servers.<name>] section in TOML. A server under the wrong key is ignored.
2. The URL key. Antigravity and Antigravity CLI use serverUrl. Claude Code, Codex, Cursor, Devin, and VS Code use url.
3. The endpoint. It is https://connect.neetoform.com/mcp/messages, with no trailing slash.
4. The syntax. A trailing comma or an unclosed brace in JSON makes the whole file unreadable.

The connection is refused or unauthorized

On an API key connection, the header must read Bearer YOUR_API_KEY, with a single space after Bearer. Check that the key is not revoked and that it belongs to the workspace you expect. Generate a new key at help.neetoform.com/articles/api-keys if you are unsure.

On an OAuth connection, remove the connector and add it again to run the sign-in from the start.

More fixes are in the NeetoForm MCP troubleshooting guide.

Frequently asked questions

Can I use NeetoForm with Claude Code?

Yes. You can connect Claude Code directly to the NeetoForm MCP server using claude mcp add, or run neetoform setup claude to let Claude Code use the NeetoForm CLI. You can also use both.

Use NeetoForm in other AI assistants

Prefer the terminal? The NeetoForm CLI reaches the same data from your shell, your scripts and your coding agent.