Web Data Forms

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.

- 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.

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.

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>

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

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.

This server is currently intended for remote Streamable HTTP usage.

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

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":{}}'

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

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

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

- 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.

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

- 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 bywdf_data_templates_submissions_createandwdf_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.

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

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

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

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

- If you do not already have the submission number, obtain it throughwdf_data_templates_submissions_searchorwdf_data_templates_submissions_list_recent.

5)wdf_data_templates_submissions_search

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

- dataTemplateId
- searchField
- searchValue
- optionallimit

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

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

6)wdf_data_templates_submissions_create

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

- dataTemplateId
- data(an object containing field IDs and values)

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

- Keys indatamust 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.

- dataTemplateId
- submissionNumber
- data(field updates)

- “Update submission 12345 and change the status field.”

- 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 indatawill be cleared to empty.
- Before calling it, retrieve the current submission values withwdf_data_templates_submissions_get,wdf_data_templates_submissions_search, orwdf_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.

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

- Valid workflow statuses
- Valid priorities
- Valid types
- Assignable users

- 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.

- dataTemplateId
- submissionNumber
- statusId
- priorityId
- typeId

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

- 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, andtypeIdare all required even if only one is changing.
- Reuse the submission’s existing values for any workflow field you do not intend to change.
- Callwdf_data_templates_submissions_get_workflow_metafirst to obtain valid IDs, and retrieve the current submission values first (usingwdf_data_templates_submissions_get,wdf_data_templates_submissions_search, orwdf_data_templates_submissions_list_recent) if you need to preserve the existing workflow state.

A good working pattern for an AI assistant is:
- Callwdf_data_templates_listto identify the available form/template.
- Callwdf_data_templates_get_schema_and_sample_submissionsto understand the fields.
- If needed, callwdf_data_templates_submissions_searchorwdf_data_templates_submissions_list_recentto find existing data.
- Create or update submissions withwdf_data_templates_submissions_createorwdf_data_templates_submissions_update.
- If workflow changes are involved, callwdf_data_templates_submissions_get_workflow_metafirst, thenwdf_data_templates_submissions_update_workflow.

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

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

- 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?",

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

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

- 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?",

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

Provide authentication in one of these ways:
- Preferred: send the headersx-api-keyandx-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.

If you see an authentication error, check that:

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