-
Lyttle_DevinHi team,
I'm using the JotForm MCP connector in Claude Cowork and all three available tool endpoints have been returning tool execution failures since approximately mid-day on April 19, 2026. The issue is consistent across multiple attempts over several hours.
Affected tools:
- create_form — fails on every attempt, including minimal single-line descriptions
- edit_form — was working earlier today (successfully added fields to form ID 261076976733064 around midday), then stopped responding entirely
- fetch — fails on both valid form IDs and fresh attempts
What we were trying to do:
- Fetch metadata from an existing form (261076976733064) to confirm its current state
- Create a new multi-page form via create_form
- Edit the existing form via edit_form as a fallback when create_form failed
Error returned: Tool execution failed. You can try again. — no additional detail, no HTTP status code surfaced to the agent.
What we've ruled out:
- JotForm's own infrastructure — status.jotform.com shows all systems operational (Forms, API, Submission Service all green)
- Description length — create_form was tested with a single sentence and still failed
- Form-specific issues — fetch fails on a known valid form ID that was successfully accessed hours earlier
Context:
- The connector worked correctly earlier today — edit_form successfully added 10 fields to form 261076976733064
- The failure appears to have started after a period of inactivity, possibly a session/token expiry or a dropped connection on the MCP server side
- No changes were made to credentials, settings, or the plugin between the working and non-working states
Request: Can you check whether the MCP server process needs a restart, whether there's a session token that's expired, or whether there's a known issue with the connector? Happy to provide any additional logs or form IDs needed to reproduce.
Thanks!
-
Podo: Support SpecialistHi Devin,
Thanks for reaching out to Jotform Support. I'm an AI assistant here to assist you.
The knowledge base includes the following relevant information about Jotform MCP:
- Jotform MCP uses OAuth 2.0 authentication to secure connections, and you can revoke client access anytime from My Account → Connected Apps → Jotform MCP → Clients.
- Authentication errors can happen if the OAuth token has expired, access was revoked, the Jotform session timed out, or workspace admin restrictions are in place.
- To fix authentication-related issues, the knowledge base says to remove the Jotform MCP connection from your client, then re-add it and complete the OAuth authorization flow again.
- Jotform MCP is currently available only as a cloud-hosted service at https://mcp.jotform.com.
- The knowledge base also notes that Jotform MCP requires an active internet connection.
- For general MCP access management, connected clients can be reviewed and revoked from your Jotform account settings.
The knowledge base does not include information confirming whether the MCP server process needs a restart or whether there is a known connector-wide issue for the date you mentioned.
I don't know this information and our support team will handle your request.
Give it a try and let us know how it goes.
-
DDean Damjanovic
-
Joeni JotForm SupportHi Dean,
I've gone ahead and moved your other question to a separate thread to keep things tidy, and someone from our Support Team will help you out with it here.
Let us know if you have any other questions.
Your Reply
Something Went Wrong
An error occurred while generating the AI response. Please try again!