Skip to main content
Which checks apply depends on how you connected, so start with the section that matches your client.

​
Claude and ChatGPT

These connect over OAuth and have no config file, so there is no key or URL typo to hunt for after the connector is created.
Check the server URL on the connector is exactly https://connect.neetoform.com/mcp/messages, with no trailing path. Remove the connector and add it again if it is wrong.
The first screen asks for a workspace subdomain, not a URL. For acme.neetoform.com, enter acme. See Workspace subdomain.You also need an account in that workspace. Signing in with an email that does not belong to it will not produce a working connection.
Name NeetoForm in the prompt, for example “List my active NeetoForm forms.” Check the connector is enabled for the conversation, and that your organization has not restricted it centrally.

​
Claude Code, Codex, Cursor, Gemini CLI, VS Code and Windsurf

These read a config file, and most failures are in it. The shapes differ per client, so check yours on Connect your assistant.
Confirm you edited the file that client actually reads:VS Code nests servers under servers, not mcpServers. Codex uses TOML rather than JSON. Restart the client after saving, and for Windsurf enable the server under Settings → Cascade → MCP Servers.
Check the URL field name for your client. Gemini CLI needs httpUrl, since it reserves url for SSE. Windsurf needs serverUrl. The others use url.Then check the URL itself is https://connect.neetoform.com/mcp/messages.
The client falls back to OAuth when it finds no credential. Add the headers block with Authorization: Bearer YOUR_API_KEY, or for Codex set bearer_token_env_var to the name of an environment variable holding the key and export it in the environment Codex runs in.
The opposite case. Remove the headers block entirely, restart the client, and approve the sign in when it prompts. For Claude Code run /mcp and pick the server; for Codex run codex mcp login neetoform.
Windsurf allows at most 100 tools across every connected server. Disable servers you are not using and reload.
It needs VS Code 1.99 or later with GitHub Copilot in Agent mode. Agent mode is what exposes MCP tools; Ask mode does not.

​
Anything that reports an authentication failure

Copy the key again from workspace settings; a truncated or wrapped key fails the same way as a wrong one. Check it has not been revoked, and that it belongs to the workspace you are trying to reach, since a key is valid in one workspace only.The header is Authorization: Bearer YOUR_API_KEY. The X-Api-Key header the REST API uses is not what MCP clients send.
Access is revoked by removing the connector, and it is also lost if your NeetoForm account is deactivated. Remove the connector and add it again to sign in fresh.

​
The assistant cannot find something you can see

One OAuth connection can cover several workspaces, and tools run against the default unless you name one. Ask “Which NeetoForm workspaces can you see?”, then name the one you mean in the prompt.An API key connection reaches exactly one workspace, the one the key belongs to.
Over OAuth every tool runs with your permissions, so a form outside your reach is missing from listings rather than returned. Viewing team members needs a role that can view them, and inviting, updating or deactivating needs one that can manage them.If you connected with an API key, no user permissions apply, so this is not the cause.
search looks at active forms and matches on title only, so an archived form or a word that appears only inside a question will not match. ListForms with a status filter reaches archived forms. ListSubmissions returns completed submissions, so a partially filled form that was never submitted does not appear.

​
Adding people fails

CreateTeamMember is all-or-nothing: if any address is malformed or the role is not one your workspace has, nobody is added. The error names the addresses at fault, or lists the roles that exist. Nothing changed, so it is safe to fix and ask again. Role names are case-sensitive and must match a role on the Roles page in workspace settings.

​
Still stuck

Ask the assistant to repeat the exact error it got from NeetoForm, and include that along with your client and whether you connected over OAuth or with an API key.