> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.neetoform.com/llms.txt
> Use this file to discover all available pages before exploring further.

# NeetoForm MCP server

> Let an AI assistant read your forms and submissions and manage your team.

NeetoForm runs a hosted [Model Context Protocol](https://modelcontextprotocol.io)
server at `https://connect.neetoform.com/mcp/messages`. Point an assistant at
that URL and it can answer questions about your forms in your own words, without
you writing a request or handling an id.

There is nothing to install and nothing to run. The server is hosted by
NeetoForm; the assistant connects to it over HTTP.

## What an assistant can do

<CardGroup cols={2}>
  <Card title="Find forms" icon="magnifying-glass">
    Search by title, or list the active, archived or favorited forms in a
    workspace.
  </Card>

  <Card title="Read submissions" icon="inbox">
    Pull completed submissions for a form, with each answer next to the question
    it responds to.
  </Card>

  <Card title="Manage the team" icon="user-group">
    List members, invite people, change roles and profile fields, and deactivate
    accounts.
  </Card>

  <Card title="Work across workspaces" icon="buildings">
    One connection can reach every workspace you approved it for. Name the one
    you mean in the prompt.
  </Card>
</CardGroup>

The full list is on the [Tools](/mcp/tools) page.

## Prerequisites

* A NeetoForm workspace and your [workspace subdomain](/getting-started/workspace-subdomain).
* An assistant that supports remote MCP servers. See
  [Connect your assistant](/mcp/connect) for the ones covered here.
* Optionally, an API key. It is needed only for workspace-scoped access, since
  every supported client can connect over OAuth instead. See
  [Authentication](/mcp/authentication).

## Pick how you connect first

The server takes two kinds of credential, and the choice decides what the
assistant can reach:

* **OAuth** scopes the connection to you, so the assistant sees what your
  account sees.
* **An API key** scopes it to the whole workspace, with no user attached.

That is a permissions boundary rather than a setup preference, so read
[Authentication](/mcp/authentication) before configuring a client.

## Where to go next

<CardGroup cols={2}>
  <Card title="Authentication" icon="shield-halved" href="/mcp/authentication">
    What OAuth and an API key each let the assistant see.
  </Card>

  <Card title="Connect your assistant" icon="plug" href="/mcp/connect">
    Server details and per client setup.
  </Card>

  <Card title="Examples" icon="comments" href="/mcp/examples">
    Prompts that work once you are connected.
  </Card>

  <Card title="Tools" icon="wrench" href="/mcp/tools">
    Every tool the server exposes.
  </Card>
</CardGroup>