Add MCP (Model Context Protocol) server support for AI agent integration

Summary

Add native MCP (Model Context Protocol) support so AI assistants (Claude, and other MCP-compatible agents) can interact with OpnForm directly — creating and managing forms, reading submissions, and updating fields — without going through screen automation or hand-rolled API glue.

Motivation

MCP is becoming the standard way AI agents connect to external tools (Anthropic, and a growing list of SaaS products — Linear, Notion, Zapier, etc. — already ship first-party MCP servers). Right now, using OpnForm from an AI agent workflow means either:

• Scripting against the REST API manually per integration, or

• Driving the web UI via browser automation

Both are brittle and have to be rebuilt per agent/tool. A first-party MCP server would let any MCP-compatible client (Claude Code, Claude Desktop, etc.) manage OpnForm forms and data as a native capability, out of the box.

Proposed solution

Ship an MCP server (either bundled with OpnForm or as a companion package) exposing tools such as:

• list_forms / get_form — read form structure and settings

• create_form / update_form — build or modify a form's fields programmatically

• list_submissions / get_submission — read response data

• delete_submission (gated/confirmable, since it's destructive)

• get_form_analytics — view counts, submission counts, completion rate

Given OpnForm already has a documented REST API, the MCP server could largely be a thin wrapper that maps these tools onto existing API endpoints — auth via the same API tokens users already generate today.

Example use cases

• "Create a customer feedback form with these 5 questions" — done conversationally, no dashboard clicking.

• An AI assistant summarizing new form submissions each morning as part of a briefing.

• Bulk-editing form field labels/options across multiple forms via natural language.

Alternatives considered

• Public REST API (already exists) — usable, but requires per-integration custom code rather than working automatically with any MCP client.

Happy to help test against a reference implementation if that's useful.