Mokaform MCP for AI. Control your entire form lifecycle from chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Mokaform connects form building and data capture directly into your agent workflow. It lets you create interactive surveys with visual logic builders that change questions based on previous answers.
Use it to manage forms across workspaces, read every response submission, or update fields without leaving your chat client.
What your AI can do
Create form
Builds and saves a brand new form template within Mokaform.
Delete response
Permanently removes a single, specific submitted response record.
Get form
Retrieves the full configuration and details for one specified form ID.
Use create_form to define a new survey or collection tool in minutes.
Modify existing forms using update_form without manual UI steps.
List all available form templates or list the workspaces they live in using list_forms and list_workspaces.
Grab full details for one single response record with get_response.
List every response submitted to a specific form using list_responses, perfect for reporting.
Remove unwanted or outdated responses from the system via delete_response.
Ask an AI about this
Waiting for input…
Mokaform MCP Server: 8 Tools for Form & Response Management
Manage the full form lifecycle—from creating new templates to retrieving specific submissions and auditing workspaces—all through natural conversation.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Mokaform on VinkiusCreate Form
Builds and saves a brand new form template within Mokaform.
Delete Response
Permanently removes a single, specific submitted response record.
Get Form
Retrieves the full configuration and details for one specified form ID.
Get Response
Fetches all data points from a single completed form submission.
List Forms
Returns a list of every active and archived form template available in your account.
List Responses
Gathers a paginated list of all submitted responses for a given form ID.
List Workspaces
Displays all the distinct organizational containers (workspaces) where your forms are stored.
Update Form
Modifies the settings, fields, or logic of an existing form template.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Mokaform integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Mokaform, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Mokaform. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 8 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Gathering feedback shouldn't require three different dashboards and five hours of copy-pasting.
Right now, gathering user input means jumping between the form builder UI, the response list view, and then manually exporting data to Excel. You spend half your time just trying to piece together which survey belongs to which client, and how many responses are actually valid.
With this MCP server, you ask for it—'Show me all Q2 feature requests.' The agent runs `list_forms` and targets the correct workspace, giving you a single, structured output of submissions. You get data, not headaches.
Mokaform MCP Server: Build dynamic forms with `create_form`.
Previously, building a survey meant logging into the tool, navigating to a workspace, selecting a template, and manually setting every field. If you needed an immediate change, you had to repeat that whole process.
Now, you just tell your agent: 'Create a new form called X in Y workspace.' The `create_form` tool handles the entire setup, letting you start collecting data minutes faster than before.
What your AI can actually do with this
Yo. This Mokaform MCP Server lets your AI client handle all your form building and data collection straight from the chat window. You never gotta open up the web UI or deal with clunky menus again; you just talk to your agent, and it makes it happen.
Your agent uses this server to manage every aspect of Mokaform—from drafting a brand-new survey to wiping out old responses. It's all about getting structured data into your workflow without leaving the chat client.
Building and Structuring Forms
Need a new form? You kick off the process using create_form, which builds and saves a whole template for you in minutes. Once that’s done, you can keep an eye on what you got with list_forms to see every active or archived survey sitting in your account. If you need to adjust something—maybe change a required field or tweak the logic—you run update_form.
This lets you modify settings, fields, and even the flow of an existing form template without having to click around in a GUI.
For deep dives into what's already set up, you can use get_form to pull the entire configuration and all the details for one specific form ID. It’s like pulling up the blueprint before you start building. And if you gotta know which organizational buckets your forms live in, run list_workspaces; that shows every distinct container where your data is stored.
Handling Responses and Data
When it comes to data, there are a few ways you'll want to play around. You can grab all the full details for one single submitted form record using get_response. This fetches every piece of data point associated with that specific submission ID. But if you're doing reporting or just wanna see everything that came through, list_responses gathers a paginated list of all submissions tied to a given form ID.
That’s killer for reports.
To get an overview of all the raw data collected across every single survey in your account, run list_forms, and you'll see the templates that generate those responses. You can also pull a full list of every submitted response record by running list_responses against a specific form ID.
Cleanup and Control
Sometimes you just gotta clear out the junk. If there’s an outdated or incorrect submission, you use delete_response to permanently remove that single, bad record from the system. You're in full control of your data hygiene with this one.
Basically, you tell your agent what you want—whether it's building a whole new survey via create_form, checking the structure of an old one using get_form, pulling up every response for reporting purposes with list_responses, or cleaning house by deleting garbage submissions. It manages all that heavy lifting in plain conversation.
019dd127-26c1-7396-a0e4-8c8b35a78ae3 
Here's how it actually works
The bottom line is, you treat form management like chatting with a colleague: you just tell it what you need done.
First, subscribe to this server and input your Mokaform API Key into your client.
Next, ask your agent a command—like 'List all forms in the HR workspace'—and let it run list_forms or list_workspaces.
The system returns the data structure for your request (e.g., 4 active forms), which you can then use to target specific actions like calling get_response.
Who is this actually for?
Product Managers who hate manually exporting data into spreadsheets. Marketing teams needing to run targeted A/B surveys. HR specialists managing high-volume, complex job applications. You're the person tired of clicking through five different dashboards just to compile a single report.
Uses list_forms and create_form to quickly prototype feedback tools for internal testing, then uses get_response to pull specific user journey data.
Manages onboarding by listing all job application forms (list_forms) and using list_responses to review the last 10 candidates submitted.
Builds lead capture surveys (create_form), checks if a specific campaign is running by listing workspaces, and uses get_response to validate key contact details.
What Changes When You Connect
Build fast: Use create_form to roll out new feedback surveys instantly. You don't need a developer to write basic CRUD endpoints—you just describe the form, and it gets built.
Audit data easily: When you need all submissions for Q3, run list_responses. This pulls every record into your agent, allowing immediate analysis without exporting CSVs.
Maintain accuracy: Use get_form before making changes. You can pull the current definition to confirm exactly which fields and logic rules are active before calling update_form.
Keep data separate: Need to segment forms for different departments? Call list_workspaces first. This keeps your HR forms totally isolated from your Marketing surveys.
Fix mistakes instantly: If a submission is incorrect or leaked, run delete_response. It handles the removal of that specific record cleanly.
See it in action
Reviewing Job Applicants
The HR manager needs to see all job applications from last week. They ask their agent, 'Show me responses for the 'Job Application' form.' The agent calls list_responses and gives them a summary of 23 submissions, allowing them to quickly identify the candidates who haven't responded yet.
Launching a New Feature Survey
A Product Manager wants to test new pricing models. They first use list_workspaces to find the 'Beta Testing' area, then call create_form to build a clean survey template for that workspace. Finally, they share the link and track submissions using get_response.
Correcting Bad Data
A marketer realizes an old survey form ('Event RSVP') is still active but contains bad data entries. They call list_forms to confirm the ID, then use update_form to disable the form and remove the problematic entries using delete_response.
Comparing Multiple Projects
A team lead needs to compare feedback across three different product lines. They ask their agent to list all forms (list_forms) and then run get_form for each one, consolidating the titles and field structures into a single comparison report.
The honest tradeoffs
Trying to update without knowing IDs
The user attempts to tell their agent: 'Change the feedback form.' The agent fails because it doesn't know which specific form ID or workspace to target.
First, run list_forms to get all available forms. Then, use the exact Form ID returned in that list when calling update_form. Always confirm IDs first.
Over-relying on memory
The user tries to delete a response but forgets if it was from the 'Beta' workspace or the main one. They just say, 'Delete that response.' The agent has no context.
Always use list_workspaces first to scope your action. Then, when you call delete_response, specify the Workspace ID and Form ID for maximum certainty.
Treating forms like static documents
The user tries to add a complex logic flow that requires multiple nested conditional jumps without updating the form structure. The API call fails because it's missing required field definitions.
If you change the logic, don't just guess; use get_form to pull the existing structure definition first. Then, pass the full, updated JSON payload when calling update_form.
When It Fits, When It Doesn't
Use Mokaform if your core bottleneck is structured data collection and form lifecycle management. You need an agent that can read submissions (list_responses), build forms dynamically (create_form), or audit existing structures (get_form).
Don't use this server if your problem is unstructured communication (e.g., processing free-text emails) — you'd need a text parsing tool for that. Also, don't rely on it for complex business logic validation; while update_form modifies the structure, Mokaform doesn't inherently validate external state changes like 'Is this user an employee?' You still need to run those checks in your primary application layer before calling any of these tools.
Questions you might have
How do I get all my submitted form responses using list_responses? +
list_responses gathers every submission for a specific form ID. You just need to tell the agent which Form ID you want data from, and it handles pagination.
Can I change an existing form without losing its settings using update_form? +
Yes, update_form lets you modify fields or logic. However, always use get_form first to grab the current JSON structure; this ensures you pass a complete payload and don't break anything.
How do I find out which workspaces I have? Do I need list_workspaces? +
You use list_workspaces. This tool shows every container where your forms are stored. It's critical to run this before you try to create or update a form, so you know the correct scope.
What is the difference between get_response and list_responses? +
list_responses gives you a summary view of every record for a whole form. get_response, however, drills down to give you all the detailed data points (e.g., rating, comments) from one specific submission.
If I use `delete_response`, am I sure that data is permanently gone? +
Yes, deleting a form response removes it entirely and cannot be recovered. The tool executes the deletion immediately upon confirmation; there's no soft-delete or trash bin feature to restore the record.
How does `get_form` help me understand the structure of a form compared to just using `list_forms`? +
Get_form returns the full schema, including every field type and validation rule. While list_forms only gives you the name and ID, get_form shows exactly how the dynamic logic works.
What parameters do I need to provide when running `create_form`? +
You must provide a unique title and specify which workspace should host the new form. The tool requires these identifiers to ensure the form is properly scoped and organized from the start.
When I use `list_workspaces`, what does that tell me about data isolation? +
This function shows you all the top-level containers where your forms live. Workspaces isolate your efforts, meaning forms and responses in one workspace won't affect those in another.
Can I create and collect form responses? +
Yes. Create forms programmatically, then list and read all submissions with full field data.
What API does Mokaform use? +
Mokaform uses Bearer authentication against api.opnform.com/v1.
Can I organize forms into workspaces? +
Yes. List and manage workspaces to keep forms organized by project or team.
We've already built the connector for Mokaform. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 8 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.