Proforms MCP for AI. Manage Field Jobs and Structured Data Collection.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Proforms connects your AI agent to a full suite of field service management tools. Build custom forms and collect structured data from sites or users.
You can list active forms, retrieve specific submissions by ID using `get_submission`, and manage the underlying job lifecycle with tools like `create_job` and `update_job`.
It's all accessible via conversation.
What your AI can do
Create job
Adds a brand-new job task for a field worker to complete.
Get asset
Pulls the full details sheet for one specific piece of registered equipment.
Get form
Retrieves all structural information about a single, defined form.
List all available forms using list_forms or pull the specific details of one form with get_form.
Pull full submission records for a single instance via get_submission, or list every data point submitted against a form using list_submissions.
Manage the job lifecycle by pushing new tasks (create_job), retrieving status updates (get_job), and modifying existing jobs in place (update_job).
List all registered equipment assets with list_assets or check the API connection health using get_me.
Ask an AI about this
Waiting for input…
Proforms MCP Server: 12 Tools for Field Management
Use these tools to create, retrieve, update, and list records across forms, jobs, assets, and users. It's your central data hub.
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 Proforms on VinkiusCreate Job
Adds a brand-new job task for a field worker to complete.
Get Asset
Pulls the full details sheet for one specific piece of registered equipment.
Get Form
Retrieves all structural information about a single, defined form.
Get Job
Gets the current status and history for an existing field job task.
Get Me
Checks if your AI client is connected correctly and verifies user context...
Get Submission
Retrieves all data points from one specific form submission record.
List Assets
Lists every single equipment asset currently registered in the system.
List Forms
Shows a list of every available mobile form you can use for data collection.
List Jobs
Provides an overview listing all active and completed field job tasks.
List Submissions
Lists the records of data submissions made against a specific form ID.
List Users
Shows every user account registered in both the back office and the field.
Update Job
Modifies key details—like status or assigned personnel—on an existing job task.
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 Proforms 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 Proforms, 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 Proforms. 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 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Collecting field data shouldn't require three different dashboards.
Today, gathering a simple report means logging into the form builder to see submissions, then jumping over to the asset management system to verify equipment status, and finally opening a ticketing tool just to confirm who was assigned. You spend more time clicking tabs than analyzing data.
With Proforms MCP Server, your agent handles all that overhead. You ask for 'Submissions for Form XYZ linked to Job ABC.' The agent pulls the form data via `get_submission` and cross-references it with job status from `get_job`. You get one clean answer.
Proforms MCP Server: Get real-time visibility into your field jobs.
Manual updates mean a manager has to email the worker, who then logs into the system and changes the status. If they forget, or if the internet drops, you lose track of the entire process until someone calls them.
Now, your agent manages that state change for you. Use `create_job` to push tasks instantly, and `update_job` when the worker confirms completion. The job status is always current.
What your AI can actually do with this
Proforms gives your AI client direct control over field data collection and operational management. You don't gotta download a massive CSV file or mess around with spreadsheets; you just talk to the system, and it pulls the exact info you need. This server connects your agent to everything related to job sites, forms, and equipment records.
Getting Set Up and Who You're Working With: Before you start collecting data, you gotta make sure your connection is solid. Use get_me to check your API credentials; it confirms if your AI client is talking to Proforms correctly. You can also run list_users to see every single user account—both the folks in the back office and those out in the field.
It gives you a full picture of who's authorized to do what.
Handling Forms and Data: Want to know what data needs collecting? Run list_forms to pull up a list of every mobile form available for use. If you need specifics on one particular form, get_form pulls all the structural details—you'll see exactly which fields are required and how the form is built.
Once people submit that data, you can dive right in. Use list_submissions to get a record of every single data set submitted against a specific form ID. If you need everything from one submission instance, get_submission pulls all the data points for just that one record.
Managing Field Jobs: This server lets your agent handle the entire job lifecycle. You can kick off work by calling create_job, which adds a brand-new task right for a field worker to tackle. To see what's going on with existing tasks, run list_jobs to get an overview of all active and finished jobs.
If you need the full status history on one specific job, use get_job. And if a job needs adjusting—maybe the assigned person changed or the status needs updating—update_job modifies those key details in place.
Tracking Equipment: You don't wanna lose track of your gear. Use list_assets to pull up a list of every piece of registered equipment in the whole system. When you know exactly which asset you need info on, get_asset pulls the full technical sheet for that specific machine. It's all about tracking physical items and making sure they're working right.
It’s All Conversational: You manage form structures, track every submission, handle job assignments, and check inventory—it happens entirely through conversation with your agent. Proforms gives you a complete, unified view of field operations that doesn't rely on manual data exports.
019dd143-17b9-734d-86c3-24e84289f04d 
Here's how it actually works
The bottom line is, your AI client handles the API calls; you just ask for the final answer.
Tell your AI agent what data you need—for example, 'Show me submissions for form XYZ.'
The agent calls the relevant tool (like list_submissions) and receives a structured JSON response containing all the requested field data.
Your agent processes this raw data and delivers it back to you in plain English or summarized markdown.
Who is this actually for?
This server is for operations managers and field service coordinators who deal with structured data in the real world. You're tired of jumping between a CRM, a ticketing system, and a spreadsheet just to get status updates. You need one place—your agent—to talk to all those systems simultaneously.
Uses list_jobs and update_job to monitor the status of dozens of open tasks across multiple crews.
Runs queries using list_submissions and summarizes trends from specific form data without exporting files.
Uses create_job to assign new, structured tasks immediately after a client submits a required feedback form.
What Changes When You Connect
Stop pulling data manually. Use list_submissions to pull all records for a form ID in one go, letting your agent summarize trends immediately.
Keep track of operations using the job tools. You can use get_job and update_job to get status updates or change job statuses without opening a web dashboard.
Never lose context. The server lets you cross-reference data: pull user details via list_users, then see which forms they submitted, all in one conversation thread.
Inventory check is instant. Instead of navigating through asset management pages, just ask the agent to list_assets and get a clean list of everything registered.
The full picture is available. You can link form data to job status by coordinating calls between get_submission and get_job. The system handles the join.
See it in action
Quickly Triage an Open Job
A field tech reports that Job ID 789 is stuck. Instead of calling the manager, you ask your agent to use get_job and then follow up with list_users to see who was last assigned. The agent confirms the job status and identifies the last person logged in.
Analyze a Client's Feedback Spike
A client complains about delivery times. You ask your agent to use list_forms to find 'Customer Survey,' then call get_submission for that form ID, and finally summarize the data to show exactly what the 50 most recent users complained about.
Onboard a New Asset
A new piece of equipment arrives. You use your agent to list_assets first (to check for duplicates), then call get_asset with the serial number, and finally run a command that internally creates the asset record.
Automate Task Handover
A job is completed. You instruct your agent to use update_job to mark it 'Complete,' which triggers the process, and then immediately call create_job for the next sequential task assigned to that field worker.
The honest tradeoffs
Downloading CSVs
The user manually navigates to the form dashboard, filters by date range, and hits 'Export to CSV.' This process is slow and requires manual data cleanup.
Just ask your agent: 'Give me all submissions for Form XYZ between June 1st and June 30th.' The agent uses list_submissions and delivers the structured data immediately.
Guessing Job Status
Checking the job status by logging into three different dashboards (CRM, Ticketing System, Asset Tracker) to see if everything lines up.
Use the dedicated tools. Ask your agent to run get_job for the ID you care about. This pulls the single source of truth for that task.
Ignoring User Context
Assuming a field worker has access to all forms and assets, leading to data security or permission errors.
Always check user permissions first. Use list_users or get_me to verify the context before running write operations like create_job or update_job.
When It Fits, When It Doesn't
Use this server if your core process involves collecting structured data from physical locations, managing field personnel tasks (jobs), and tracking tangible assets. The interaction between forms and jobs is key here.
Don't use it if you just need to search a repository of internal documents or knowledge articles—you’d be better off with a vector database lookup tool. Also, don't rely on it for simple message sending; that requires messaging tools. Use this when the data structure itself (the form) and the operational status (the job) are equally important parts of your workflow.
Questions you might have
Can I list all responses for a specific form? +
Yes, provide the Form ID and the agent will fetch all recent submissions and their data fields.
How do I find out which forms are currently active? +
Ask the AI to list your forms. It will display all your workspaces' forms with their current status.
Does it support creating forms automatically? +
The current scope focuses on data retrieval and submission analysis. Form creation must be done via the Proforms UI.
How do I check if my API credentials are working? Can I use the `get_me` tool? +
Use get_me to verify connectivity immediately. It returns your user context and confirms the API connection status, so you know right away if the link is solid.
Do I need a special command to list all registered equipment assets? Should I use `list_assets`? +
Just call list_assets. You'll get a manifest of every piece of equipment asset registered in the system, including details you need for tracking.
How do I modify or update an existing field job? Should I use `update_job`? +
Use update_job. You provide the Job ID and the new parameters—like changing a status or adding notes. This modifies the task record directly.
If I only have one job ID, how do I get all its details? Should I use `get_job`? +
Run get_job with that specific Job ID. It pulls all current status information, the task description, and any assigned personnel data points for you to review.
How do I see who is registered in the system? Can I use `list_users`? +
Call list_users. This gives you a full roster of all users, covering both back-office staff and field workers. It helps confirm user roles and details.
We've already built the connector for Proforms. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 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.