mcp

The Jotform MCP Server is exposed as a hosted endpoint at https://mcp.jotform.com. It provides a set of MCP-compatible tools that allow clients to discover Jotform Forms and Submissions, create and edit forms, and submit data to existing forms. Because this is a hosted service, there is no local server process to run; instead, clients connect to the remote endpoint to perform operations such as listing forms, retrieving submissions, creating new forms, and submitting data. Tools exposed by the service include list_forms, get_submissions, create_form, edit_form, create_submission, and assign_form, enabling a broad set of form-management workflows through MCP-compatible clients.

Prerequisites:

• An MCP client (Gemini CLI, Cursor IDE, Claude Desktop, or VS Code MCP extension) installed on your machine or IDE
• A Jotform account with proper OAuth permissions for the MCP integration

1. Use the hosted endpoint (no server installation required)
   • URL: https://mcp.jotform.com
2. Configure your MCP client to point at the hosted endpoint
   • In your MCP client, add the Jotform MCP server URL as the target endpoint
3. Authenticate
   • Initiate the OAuth flow as prompted by your MCP client to authorize access to your Jotform data
4. Start using tools
   • Once authenticated, you can run commands such as list_forms, get_submissions, create_form, edit_form, create_submission, and assign_form through your MCP client

Notes:

• OAuth 2.0 is required for all connections; bearer-token access is not supported
• Ensure you have the appropriate scopes granted for the operations you intend to perform

Tips and common issues:

• OAuth setup is mandatory for each user; ensure you complete the consent flow in the Jotform OAuth screen
• Rate limits apply per user, consistent with the Jotform REST API (e.g., Free tier 60 requests/min, Enterprise higher). If you exceed limits, responses may include HTTP 429 with a Retry-After header
• Since this is a hosted service, there is no local server to configure; focus on client-side configuration and OAuth permissions
• Access control is managed via OAuth scopes; only granted scopes are available to the client
• If you encounter issues, verify that your OAuth app is connected and that the hosted endpoint URL is correctly configured in your MCP client