Jotform

Yes. Jotform's developer documentation states the MCP server carries no additional charge, and that your existing plan limits and features stay in effect. So the connector itself costs nothing, but the account it reaches is still bound by whatever form, submission and API-call ceilings your plan already imposes. We read no prices from Jotform's pricing page, which renders client-side.

Yes. Jotform's REST API documents newly created forms carrying status ENABLED, and every Jotform form has a public URL from the moment it exists. There is no draft state and no approval step in the documented flow. The agent creates a reachable form; it does not distribute the link, so exposure starts when a human shares it.

Yes, through assign_form. Jotform's Assign Form feature sends email invitations to addresses you name, up to 100 per batch, and recipients must sign in to a Jotform account to open the form. This is the one tool in the list that reaches outside your account, so treat an assign request as an outbound send rather than a filing action.

It writes a response into the form as though a respondent filled it in. Jotform's REST API exposes a submissions POST endpoint that adds a record to the form's submission set, which then counts toward your plan's monthly submission usage. Jotform does not document whether this path fires notification emails, autoresponders or webhooks, so assume it might.

Yes, with conditions. Jotform's documentation says the MCP server respects your account's compliance settings, and that HIPAA-protected data is reachable only on a HIPAA-enabled plan when you explicitly grant scopes covering protected health information. Unlike some connectors, Jotform does not hard-block HIPAA accounts. The two published scopes are readOnly and full, neither PHI-specific.

No. Jotform's MCP documentation states plainly that bearer-token access is not supported and that OAuth 2.0 is required for every connection. That holds even though Jotform's REST API is API-key based, so an existing key from your account settings will not authenticate an MCP client. Every user authorises once, and only workspace admins can install the app.

Open My Account, then Connected Apps, select Jotform MCP, and choose Clients. Every OAuth-connected client is listed there. Use the overflow menu beside an entry and select Revoke; Jotform documents the client losing access immediately. The authorization server also publishes a revocation endpoint, so a client can drop its own token independently.

They are two separate servers with different tool sets. The plain MCP server at mcp.jotform.com is text-only and documents five tools. The MCP App endpoint that Anthropic lists adds interactive UI, rendering form previews and submission tables inside clients that support it, and documents nine tools. Anthropic's directory lists eleven, the union of both.