Jotform MCP
A Model Context Protocol (MCP) server for Jotform. This integration exposes Jotform Forms and Submissions to any MCP-compatible client via a hosted endpoint. It follows the Model Context Protocol spec for interoperability. The service is actively optimized based on real-world usage and more tools are coming soon. Point any MCP-enabled client to this address to begin. Ask your AI assistant to: 🗂️…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
A Model Context Protocol (MCP) server for Jotform. This integration exposes Jotform Forms and Submissions to any MCP-compatible client via a hosted endpoint. It follows the Model Context Protocol spec for interoperability. The service is actively optimized based on real-world usage and more tools are coming soon. Point any MCP-enabled client to this address to begin. Ask your AI assistant to: 🗂️ List Forms — "List all active forms created this month." 📄 Query Submissions — "Show submissions…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.