6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Build and edit Jotform Apps — published portals that collect real submissions.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Jotform Apps MCP server lets Claude, ChatGPT and other MCP agents build and edit Jotform Apps — published multi-page portals that bundle forms, payments and donations behind a shareable link. An agent creates an app from a description, then refines its pages in conversation. Sign-in is OAuth, and the write scope is all-or-nothing.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
permissions field at all, while listing two write tools and a REST dispatcher. The usual Read / Read and write signal is simply not there.mcp_app_request reaches Jotform's documented REST endpoints across five HTTP verbs. Any risk assessment based on "six tools" is sized wrong.mcp_app_request is documented only for a sibling server. Jotform describes it, and its private marking, on the Sign tab. Whether the Apps server applies the same marking is not stated anywhere we could find.readOnly and full are the only scopes advertised. There is no app-only write scope, so granting edit rights grants account-wide rights.No. Jotform runs four separate MCP endpoints and this is one of them. Jotform's developer page documents a standard server at mcp.jotform.com for forms and submissions, plus three interactive variants: Jotform for forms, Jotform Apps for portals, and Jotform Sign for signable documents. Each has its own URL and its own tool set, so connecting one gives you none of the others.
Yes. Jotform documents edit_app as editing an existing app from instructions, with a visual editor for pages and elements, and nothing in the documentation restricts it to drafts. Jotform Apps are published portals shared by link or QR code that bundle forms, payments and donations, so an edit reaches whatever your users see next.
It is a general-purpose dispatcher over Jotform's REST API. Jotform's own table describes it as a fallback for documented REST endpoints across GET, POST, PUT, PATCH and DELETE when no dedicated tool covers the action, limited to your account and granted scopes. That single entry makes the real write surface the whole API, not the five named tools beside it.
No — the record carries no permissions field at all. Most catalogue entries show a Read or Read and write label; this one shows nothing, while listing create_app, edit_app and a REST dispatcher among its six tools. Read the tool list rather than the missing label, and treat this connector as write-capable by default.
Jotform's MCP documentation does not say. It is silent on HIPAA-enabled accounts, on FERPA, and on whether MCP access is gated for either, even though Anthropic lists this connector under health-life-sciences and education. Jotform sells HIPAA-enabled forms with a Business Associate Agreement separately, but never connects that programme to MCP. Ask Jotform before connecting a regulated account.
Two, and only one of them is narrow. The server's own RFC 9728 descriptor advertises readOnly and full, verified live on 2026-08-19. There is no separate app-write or forms-only scope, so an agent that needs to create or edit anything must be granted full — which covers every Jotform resource your account can reach, not just apps.
Jotform does not state a plan requirement for this connector. Its requirements list names three things: a Jotform account with access to Jotform Apps, a client that can render interactive UI, and one-time OAuth approval. Jotform's separate note on the standard MCP server adds that only workspace admins can install the underlying Jotform MCP app.
POST to the endpoint returns HTTP 401 with body {"message":"NO_AUTH_HEADER"}; GET returns 401 · retrieved 2026-08-19/mcp-jotform-apps-v1 path-insert form (both 200, fetched 2026-08-19); the path-append form returns 401 · retrieved 2026-08-19https://oauth2.jotform.com) · retrieved 2026-08-19www.jotform.com/robots.txt allows /developers/ and /products/, names a sitemap, and carries no Content-Signal directives; /llms.txt returns 404 (fetched 2026-08-19) · retrieved 2026-08-19Connect Jotform Apps once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.