Web Data Forms

Give AI assistants secure access to your organization's structured business data. Search records, create and update records, retrieve schema information, and manage workflow states using natural language.

GitHub

दस्तावेज़

Web Data Forms MCP Server Instructions

Connect AI assistants like Claude and ChatGPT to your Web Data Forms account so they can search submissions, create new submissions, update existing data, and manage workflows using natural language.

For example, use commands like:

"Find John Smith's contact details."
"Create a new support request."
"Show me this week's inspection reports."
"Update the workflow status to Completed."
"Create a new employee leave request."

The server is designed to be stateless. It does not store your credentials. Instead, credentials are passed at runtime for each request.

For more information about Web Data Forms, visit https://www.webdataforms.com.

What this server can do

This server exposes the following tools:

wdf_data_templates_list — list automation-enabled Data Templates (Forms) available for the current group so you can identify the right Data Template (Form) before working with submissions.
wdf_data_templates_get_schema_and_sample_submissions — retrieve a form’s field definitions, searchable-field definitions, and representative sample submissions.
wdf_data_templates_submissions_list_recent — list recent submissions for a specific Data Template (Form) when you want an overview rather than a targeted search.
wdf_data_templates_submissions_get — retrieve the full contents and metadata of a specific submission by Submission Number.
wdf_data_templates_submissions_search — search submissions by a searchable field value, using values that are explicitly marked searchable on the Data Template (Form).
wdf_data_templates_submissions_create — create a new submission for a Data Template (Form) using field IDs from the schema.
wdf_data_templates_submissions_update — update an existing submission, with the caveat that it replaces the entire submission data object rather than merging changes.
wdf_data_templates_submissions_get_workflow_meta — retrieve the valid workflow statuses, priorities, types, and assignable users for the current group.
wdf_data_templates_submissions_update_workflow — replace a submission’s workflow state with the exact status, priority, type, assignee, and comment values you provide.

Setup

Required credentials

You need two values for every request:

x-api-key — your Web Data Forms API Key
x-group-id — your Web Data Forms Group ID

You can find these in your Web Data Forms accounts group->information page.

Preferred method: request headers

When possible, pass the credentials as HTTP headers:

x-api-key: <your-api-key>
x-group-id: <your-group-id>

This is the preferred option because it keeps credentials out of the URL and is more secure.

Fallback method: query parameters

If your MCP client does not support custom headers, the server also accepts the credentials as URL query parameters:

?x-api-key=<your-api-key>&x-group-id=<your-group-id>

Example:

https://mcp.webdataforms.com?x-api-key=abc123&x-group-id=xyz456

Current deployment model

At this time, the server is intended to be used through the remote hosted endpoint only. Local stdio usage is not the supported path for end users.

If your client cannot send custom headers, use the query-parameter fallback described above.

Transport options

This server is currently intended for remote Streamable HTTP usage.

Remote Streamable HTTP transport

Use this for all supported deployments.

The HTTP endpoint is:

https://mcp.webdataforms.com

How to connect to the server

Remote-only connection

Connect your MCP client to the hosted remote URL and send the credentials as headers when supported.

Example with headers:

curl -X POST "https://mcp.webdataforms.com" \
  -H "Content-Type: application/json" \
  -H "x-api-key: your-api-key" \
  -H "x-group-id: your-group-id" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Example using query parameters as a fallback:

curl -X POST "https://mcp.webdataforms.com?x-api-key=your-api-key&x-group-id=your-group-id" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Tools

1) `wdf_data_templates_list`

Use this first when you need to discover which automation-enabled Data Templates (Forms) are available in the current group.

Typical use case:

“List the Data Templates (Forms) available in my group.”
“Show me the Data Templates (Forms) I can work with.”

What it returns:

A list of available Data Templates (Forms) for the active group.

Best practice:

Call this before trying to create, search, or update submissions so you can identify a valid Data Template ID.

2) `wdf_data_templates_get_schema_and_sample_submissions`

Use this whenever you need to understand a Data Template (Form) structure before creating, updating, or searching submissions.

Required input:

dataTemplateId

What it returns:

The form’s fields, including their field IDs
The searchable fields that can be used with wdf_data_templates_submissions_search
Representative sample submissions that show expected structure and values

Best practice:

Always use this before creating a new submission if you need to know which fields are required or supported.
The field IDs returned here are the exact keys expected by wdf_data_templates_submissions_create and wdf_data_templates_submissions_update; use them rather than display labels.

3) `wdf_data_templates_submissions_list_recent`

Use this to browse or review recent submissions for a Data Template (Form) when you do not need a targeted search.

Required input:

dataTemplateId
optional limit

Typical use case:

“Show me the last 10 submissions for this Data Template (Form).”

Best practice:

Use this when you need an overview or want to inspect recent record shapes before editing or creating new ones.

4) `wdf_data_templates_submissions_get`

Use this when you already know the Submission Number and want the full contents and metadata for that submission.

Required input:

dataTemplateId
submissionNumber

Typical use case:

“Get submission 12345 from Data Template (Form) ABC123.”

Best practice:

If you do not already have the submission number, obtain it through wdf_data_templates_submissions_search or wdf_data_templates_submissions_list_recent.

5) `wdf_data_templates_submissions_search`

Use this to find existing submissions by a searchable field value.

Required input:

dataTemplateId
searchField
searchValue
optional limit

Typical use case:

“Find submissions where the customer name is Jane Doe.”

Important note:

Only fields marked as searchable in the Data Template (Form) schema can be used here.
Call wdf_data_templates_get_schema_and_sample_submissions first to confirm which fields are searchable.

6) `wdf_data_templates_submissions_create`

Use this to create a new submission for a Data Template (Form).

Required input:

dataTemplateId
data (an object containing field IDs and values)

Typical use case:

“Create a new submission for Data Template (Form) ABC123 with these values.”

Important details:

Keys in data must match the field IDs from the template schema, not display labels.
Unrecognized keys may be silently dropped rather than raising an error.
Include fields marked as required in the schema; omitted optional fields are simply left blank on the new submission.

7) `wdf_data_templates_submissions_update`

Use this to modify an existing submission.

Required input:

dataTemplateId
submissionNumber
data (field updates)

Typical use case:

“Update submission 12345 and change the status field.”

Important details:

This tool replaces the submission’s entire data object with the values you provide; it is a full overwrite, not a merge.
Any existing field not included in data will be cleared to empty.
Before calling it, retrieve the current submission values with wdf_data_templates_submissions_get, wdf_data_templates_submissions_search, or wdf_data_templates_submissions_list_recent, then include the full set of fields you want to preserve along with the ones you are changing.
Field IDs must match the template schema; use the schema tool to confirm them.

8) `wdf_data_templates_submissions_get_workflow_meta`

Use this before updating workflow values if you do not already know the valid status, priority, type, and user values.

Typical use case:

“What workflow statuses and assignees are valid for this group?”

What it returns:

Valid workflow statuses
Valid priorities
Valid types
Assignable users

Best practice:

Call this before any workflow change if the valid values are not already known.

9) `wdf_data_templates_submissions_update_workflow`

Use this to change workflow properties such as status, priority, type, and assignee for a specific submission.

Required input:

dataTemplateId
submissionNumber
statusId
priorityId
typeId

Optional input:

assigneeUserId
comment

Typical use case:

“Update the workflow for submission 12345 to status X and priority Y.”

Important details:

This tool replaces the submission’s workflow state with the exact values you provide; it is a full overwrite, not a partial update.
statusId, priorityId, and typeId are all required even if only one is changing.
Reuse the submission’s existing values for any workflow field you do not intend to change.
Call wdf_data_templates_submissions_get_workflow_meta first to obtain valid IDs, and retrieve the current submission values first (using wdf_data_templates_submissions_get, wdf_data_templates_submissions_search, or wdf_data_templates_submissions_list_recent) if you need to preserve the existing workflow state.

Recommended workflow for agents

A good working pattern for an AI assistant is:

Call wdf_data_templates_list to identify the available form/template.
Call wdf_data_templates_get_schema_and_sample_submissions to understand the fields.
If needed, call wdf_data_templates_submissions_search or wdf_data_templates_submissions_list_recent to find existing data.
Create or update submissions with wdf_data_templates_submissions_create or wdf_data_templates_submissions_update.
If workflow changes are involved, call wdf_data_templates_submissions_get_workflow_meta first, then wdf_data_templates_submissions_update_workflow.

This sequence helps avoid invalid field names and incorrect workflow values.

Using this MCP server with Claude

Claude with the remote HTTP endpoint

Point Claude to the hosted server at:

https://mcp.webdataforms.com

Then provide the credentials as:

headers: x-api-key and x-group-id
or query parameters if the client cannot send headers

Recommended Claude usage pattern

Ask Claude to:

remember which information is stored in Web Data Forms - e.g. "For future reference, please remember that i store my contacts, expenses and open issues in Web Data Forms",
perform tasks by writing or speaking naturally - e.g. "Can you get me John Smiths' phone number?",

Using this MCP server with ChatGPT

If your ChatGPT environment supports MCP connections, configure it to connect to the hosted server endpoint and pass credentials as headers whenever possible.

Recommended setup:

Use the Streamable HTTP endpoint: https://mcp.webdataforms.com
Add the auth headers x-api-key and x-group-id
If your client does not permit custom headers, use the fallback query parameter approach

Example connection target:

https://mcp.webdataforms.com

Recommended ChatGPT usage pattern

Ask the model to:

remember which information is stored in Web Data Forms - e.g. "For future reference, please remember that i store my contacts, expenses and open issues in Web Data Forms",
perform tasks by writing or speaking naturally - e.g. "Can you get me John Smiths' phone number?",

Using this MCP server with OpenClaw

OpenClaw should be configured to connect to the MCP endpoint at:

https://mcp.webdataforms.com

Provide authentication in one of these ways:

Preferred: send the headers x-api-key and x-group-id
Fallback: append ?x-api-key=...&x-group-id=... to the URL

If OpenClaw supports a server config object or connection settings, use the equivalent of:

{
  "url": "https://mcp.webdataforms.com",
  "headers": {
    "x-api-key": "your-api-key",
    "x-group-id": "your-group-id"
  }
}

If the client cannot set headers, use the query parameter variant instead.

Using this MCP server with Smithery

https://smithery.ai/servers/dotzcominc/web-data-forms

Troubleshooting

Authentication failed

If you see an authentication error, check that:

x-api-key is present and valid
x-group-id is present and valid
you are using the correct transport
if the client cannot send headers, the query parameter fallback is being used correctly

Missing template or schema

If a template ID appears invalid:

list templates again
verify you are using the correct group
verify that the template is automation-enabled

Workflow update errors

If workflow updates fail:

call wdf_data_templates_submissions_get_workflow_meta first
verify the status/priority/type IDs are valid
confirm the assignee user ID is valid if provided

Security notes

Never hardcode credentials into source code or public repositories.
Prefer header-based auth over query parameters when the client supports it.
If you are deploying this server publicly, ensure the endpoint is only used by trusted clients.
The server does not store user credentials; it expects them on each request.

Quick summary

The fastest way to use this MCP server is:

Connect to the server with your credentials.
Use headers first, query parameters only as a fallback.
Start with wdf_list_data_templates.
Inspect the schema with wdf_data_templates_get_schema_and_sample_submissions.
Search, create, update, or change workflow state as needed.

Web Data Forms

दस्तावेज़

Web Data Forms MCP Server Instructions

What this server can do

Setup

Required credentials

Preferred method: request headers

Fallback method: query parameters

Current deployment model

Transport options

Remote Streamable HTTP transport

How to connect to the server

Remote-only connection

Tools

1) wdf_data_templates_list

2) wdf_data_templates_get_schema_and_sample_submissions

3) wdf_data_templates_submissions_list_recent

4) wdf_data_templates_submissions_get

5) wdf_data_templates_submissions_search

6) wdf_data_templates_submissions_create

7) wdf_data_templates_submissions_update

8) wdf_data_templates_submissions_get_workflow_meta

9) wdf_data_templates_submissions_update_workflow

Recommended workflow for agents

Using this MCP server with Claude

Claude with the remote HTTP endpoint

Recommended Claude usage pattern

Using this MCP server with ChatGPT

Recommended ChatGPT usage pattern

Using this MCP server with OpenClaw

Using this MCP server with Smithery

Troubleshooting

Authentication failed

Missing template or schema

Workflow update errors

Security notes

Quick summary

1) `wdf_data_templates_list`

2) `wdf_data_templates_get_schema_and_sample_submissions`

3) `wdf_data_templates_submissions_list_recent`

4) `wdf_data_templates_submissions_get`

5) `wdf_data_templates_submissions_search`

6) `wdf_data_templates_submissions_create`

7) `wdf_data_templates_submissions_update`

8) `wdf_data_templates_submissions_get_workflow_meta`

9) `wdf_data_templates_submissions_update_workflow`