# AI-assisted Process Design Plugin

**URL:** <https://discuss.workflowgen.com/t/ai-assisted-process-design-plugin/2382>\
**Category:** Process Design\
**Created:** [November 11, 2026, 2:11am UTC](https://discuss.workflowgen.com/t/ai-assisted-process-design-plugin/2382 "2026-11-11T02:11:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wfg-admin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/wfg-admin/32/714_2.png) [@wfg-admin](https://discuss.workflowgen.com/u/wfg-admin)\
**Post date:** [November 11, 2026, 2:11am UTC](https://discuss.workflowgen.com/t/ai-assisted-process-design-plugin/2382/1 "2026-11-11T02:11:13Z")

</div>

## Getting Started

Install the WorkflowGen Process Design skill from the supplied plugin, then connect your client to your organization’s WorkflowGen server. Follow the section for your client: [Claude Cowork](#claude-cowork), [ChatGPT Work](#chatgpt-work) or [Cursor](#cursor).

**WorkflowGen 10.6.0 Beta:** See the [release notes on the WorkflowGen forum](https://discuss.workflowgen.com/t/workflowgen-v10-6-0-beta) for the feature scope, installation packs, plugin download, upgrade guide and documentation. All three clients use the same plugin archive: Claude Cowork and ChatGPT Work import the ZIP, while Cursor installs its included skill manually.

**Scope:** This guide covers macOS and Windows desktop setup. The package contains the skill and instructions; it does not install the WorkflowGen server. The MCP connection is configured separately. Menu labels can vary with your client version and organization’s settings.

**Before use:** Back up process definitions and verify planned changes on a development or test installation before applying them to operational processes.

Plugin **0.1.0** includes process-design skill **0.2.30**. WorkflowGen 10.6.0 includes MCP Server **1.1.0**. No separate skill download is required.

## Requirements

**OpenID Connect (OIDC) or SAML is required.** The main WorkflowGen site must use one of these two authentication modes for browser sign-in. They are the only supported WorkflowGen authentication modes for the plugin’s MCP connection.

Your administrator must also enable **OAuth access on the WorkflowGen MCP server**. OAuth authorizes the assistant’s MCP access after you sign in to WorkflowGen through OIDC or SAML.

Other WorkflowGen authentication modes, including Windows, Basic, Applicative, Form and custom authentication modules, are **not supported for this MCP connection**. Being able to sign in to the WorkflowGen portal with one of these modes does not meet the MCP authentication requirement.

## Before you begin

Have the supplied plugin ZIP, your WorkflowGen account and the full HTTPS MCP server address supplied by your administrator ready. Use an account and workspace that allow the required plugin or skill and remote MCP connection.

When authentication opens your browser, sign in, review the requested access and click **Authorize** yourself. Read access is sufficient for the connection check below; creation or editing requires the corresponding access. Do not send your password or access tokens to the assistant. This sign-in is separate from approving individual tool calls and from signing in to WorkflowGen for browser display.

| Client | Desktop application requirements on macOS and Windows |
| --- | --- |
| Claude Cowork | Install [Claude Desktop](https://support.claude.com/en/articles/10065433-install-claude-desktop), sign in and select Cowork when offered. In the unified Claude experience, start from a new conversation. Cowork requires an eligible paid plan and permission to use custom plugins and connectors. |
| ChatGPT Work | Install the [ChatGPT desktop app for macOS](https://learn.chatgpt.com/docs/app) or [Windows](https://learn.chatgpt.com/docs/app/windows), sign in and select Work. Your account and workspace must permit Work, custom plugins and MCP connections. Desktop-control features are not required for the remote WorkflowGen connection. |
| Cursor | Install Cursor for your operating system, sign in and open Agent on your local computer. Use a version and account that support Agent Skills and remote MCP connections. A local WorkflowGen source repository is not required. |

## Claude Cowork

### 1 · Install the plugin

1. Open **Customize → Plugins**. In versions that place Customize under Settings, open **Settings** first.
2. Select **Add → Upload plugin** and choose the supplied **WorkflowGen Process Design plugin ZIP**. Keep the ZIP as it is; there is no need to extract it.
3. Click **Upload** and check that **WorkflowGen Process Design** is enabled.

The plugin provides the process design skill. Add your WorkflowGen connection separately in the next step.

Ask your administrator to confirm that the supplied HTTPS MCP address is reachable by Claude’s remote connector service. An address reachable only from your computer or a private VPN is not sufficient for this connection. See [Anthropic’s network requirements](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

### 2 · Add your WorkflowGen connection

1. Open **Customize → Connectors** , select **Add** , then **Custom → Web** (or **Add custom connector** in earlier versions).
2. Enter the following details:

| Field | Value |
| --- | --- |
| Name | WorkflowGen |
| URL | The full HTTPS MCP server address supplied by your administrator |

Example address (replace the full URL with the one supplied by your administrator):

`https://server.example.com/wfgen/mcp`

1. Click **Continue** , review the detected authentication settings and click **Continue** again if shown.
2. Under **Authentication** , select **Sign in now**. Under **OAuth client** , select **Register automatically**.
3. Leave **Request headers** empty and click **Add**.
4. Complete the browser sign-in and **Authorize** step with your WorkflowGen account when prompted.
5. Open the connector’s **Tool permissions** to configure the tool approvals described below.

After connecting, continue with [Check your connection](#check-your-connection).

## ChatGPT Work

### 1 · Install the plugin

1. Open **Customize → Plugins**. In versions that place the directory under Settings, use **Settings → Plugins → Browse directory**.
2. Select **Add → Upload plugin archive**.
3. Choose the supplied **WorkflowGen Process Design plugin ZIP** and click **Add plugin**. Keep the ZIP as it is; there is no need to extract it.
4. On the **WorkflowGen Process Design** page, click **Install plugin**.

The plugin provides the process design skill. Add your WorkflowGen connection separately in the next step.

### 2 · Add your WorkflowGen connection

1. Open **Settings → MCP servers**. In versions that group connections under plugins, use **Settings → Plugins → MCPs**.
2. Select **Add server** or **Add → Add MCP server** , depending on your version.
3. Enter the following details:

| Field | Value |
| --- | --- |
| Name | WorkflowGen |
| Type | **Streamable HTTP** |
| URL | The full HTTPS MCP server address supplied by your administrator |

Example address (replace the full URL with the one supplied by your administrator):

`https://server.example.com/wfgen/mcp`

1. Leave **Bearer token env var** , **Headers** and **Headers from environment variables** empty for this sign-in setup.
2. Click **Save** , then **Restart** if offered to reload the connection.
3. Click **Authenticate** when the server requires sign-in. If the button is missing, fully quit and reopen ChatGPT Work, then return to the WorkflowGen MCP connection and click **Authenticate**.
4. Complete the browser sign-in and **Authorize** step with your WorkflowGen account when prompted.

See the [ChatGPT desktop MCP setup documentation](https://learn.chatgpt.com/docs/extend/mcp) for the current connection controls.

After connecting, continue with [Check your connection](#check-your-connection).

## Cursor

### 1 · Install the skill

#### macOS

1. In Finder, double-click the supplied **WorkflowGen Process Design plugin ZIP** to extract it.
2. Open the extracted plugin folder, then **skills → workflowgen-process-design**. This is the skill inside the plugin: it contains **SKILL.md** and the **references** folder.
3. Open another Finder window. Choose **Go → Go to Folder…** (Command + Shift + G), enter `~/.cursor/` and press Return. The `.cursor` folder is hidden; this shortcut opens it directly. If Finder cannot find it, open Terminal, run `mkdir -p ~/.cursor/skills/workflowgen-process-design`, then repeat the Finder shortcut. This creates the skill folders in your user account without replacing existing files.
4. Inside `.cursor`, create a folder named exactly **skills** if it does not exist: choose **File → New Folder** (Command + Shift + N), then enter `skills`.
5. Open **skills** and create a folder named exactly **workflowgen-process-design** if it does not exist.
6. Copy **SKILL.md** and the complete **references** folder from step 2 into this new folder. Preserve all subfolders and files inside **references**. Select the items, press Command + C, click the destination window and press Command + V.

The resulting structure must be:

```plaintext
~/.cursor/skills/workflowgen-process-design/
  SKILL.md
  references/
    …all supplied reference files and subfolders…

```

Return to Cursor and open **Customize → Skills**. Check that **workflowgen-process-design** appears. If it does not, fully quit and reopen Cursor, then check again. Open the skill to view its instructions and metadata version.

#### Windows

1. In File Explorer, right-click the supplied **WorkflowGen Process Design plugin ZIP** and select **Extract All…** , then **Extract**.
2. Open the extracted plugin folder, then **skills → workflowgen-process-design**. Keep this window open; it contains **SKILL.md** and **references**.
3. Open another File Explorer window. Click its address bar, enter `%USERPROFILE%\.cursor` and press Enter. If the folder does not exist yet, open `%USERPROFILE%`, create a folder named `.cursor`, then open it.
4. Create a folder named exactly **skills** if it does not exist, using **New → Folder** or **Ctrl + Shift + N**.
5. Open **skills** , then create and open a folder named exactly **workflowgen-process-design** if it does not exist.
6. Copy **SKILL.md** and the complete **references** folder from step 2 into that folder, using **Ctrl + C** and **Ctrl + V**. Preserve all reference subfolders and files.
7. Return to **Customize → Skills** in Cursor and check that **workflowgen-process-design** appears. Fully quit and reopen Cursor if needed.

The destination is `%USERPROFILE%\.cursor\skills\workflowgen-process-design\SKILL.md`, with **references** beside **SKILL.md**.

Use the skill contained in the supplied plugin; a separate skill download is not needed. **Skills → New** creates a blank skill. This procedure installs the supplied skill manually and does not use **Plugins → Add → From Local Repository** , which expects a marketplace catalogue. Local use does not require cloud synchronization.

### 2 · Add your WorkflowGen connection

1. Open **Customize → MCPs → New MCP Server**. Cursor opens your user `mcp.json` configuration.
2. Add the following **WorkflowGen** entry under `mcpServers`, replacing the example URL with the full HTTPS address supplied by your administrator. If other servers are already configured, preserve their entries; do not replace the whole file.

```json
{
  "mcpServers": {
    "WorkflowGen": {
      "url": "https://server.example.com/wfgen/mcp"
    }
  }
}

```

1. Save the file with **Command + S** on macOS, **Ctrl + S** on Windows, or **… → Save File**.
2. Return to **Customize → MCPs**. When WorkflowGen shows **Needs authentication** , click **Authenticate**.
3. In the browser, sign in with your WorkflowGen account, select the access required for your work and click **Authorize**. Read access is sufficient for the connection check below; process creation or editing needs the corresponding write scopes and native account permissions.
4. Return to Cursor and check that WorkflowGen shows **Connected** and its tools are listed. Click **Done** to close the configuration panel.

See Cursor’s [Agent Skills](https://cursor.com/docs/skills) and [MCP configuration](https://cursor.com/docs/mcp) documentation for its current host setup options.

After connecting, continue with [Check your connection](#check-your-connection).

## Check your connection

Start a new Cowork task in Claude (or a new conversation in the unified experience), a new Work chat in ChatGPT or a new local Agent chat in Cursor. Send:

> Use the workflowgen-process-design skill and the WorkflowGen MCP connection. Call only get\_viewer to identify my connected account. Show my name and account status. Do not modify any data. If the tool is unavailable, explain the blockage. Do not inspect the local project repository.

Approve the tool call if prompted. If the expected account details are returned, **your connection is working**. This check does not create or change a process and does not establish write access.

If the skill is unavailable, check that the plugin is enabled in Claude or installed in ChatGPT. In Cursor, check that the complete skill and its references are in the folder described above. If the MCP tool is unavailable, check the separate connection and authentication, restart the client if needed, then try in a new task or chat.

### If a form or file is too large

Send the reported size error to your WorkflowGen administrator. WorkflowGen 10.6.0 recommends **32 MiB** for the MCP and Administration request limits; existing or inherited installation settings may be lower or higher, and omitting those settings does not automatically select 32 MiB. The ceiling covers the complete encoded request, including its envelope and encoding overhead, so the file or HTML that fits depends on how it is sent. Existing stored content can also prevent a read or replacement after a limit is lowered. The administrator can review the applicable limits using the release’s upgrade guide; installing the plugin does not change them.

## Start using WorkflowGen

Describe the process you want to explore or design in your own words.

- **To consult information:** allow the required read tools.
- **To create or edit processes:** also allow the required write tools and ensure your WorkflowGen account has the corresponding access.

Choose approval settings that suit your work:

- **Claude and ChatGPT:** choose per-call confirmation or persistent tool permissions in the available approval controls. Persistent approval is optional, and workspace policies can restrict it.
- **Cursor:**  **Run** approves the current call. **Always Run** , when offered, remembers approval for that tool; other tools may still require approval.

For sensitive write tools, such as publishing server code, deleting requests or changing accounts, keep confirmation enabled when configuring persistent tool approvals. Content read from processes, comments or shared templates may come from other users; it does not authorize additional actions on your behalf.

Approving a tool in the client does not grant access in WorkflowGen. Ask your administrator to authorize the connection for the work you need: reading information, making changes or designing processes. Your WorkflowGen account must also have the corresponding permissions. Sign in again if requested after an access change.

Process designers can modify authorized processes within their managed folders; application and category creation requires a WorkflowGen administrator. Native process-state rules still apply. Shared field templates can affect several processes. As in the native interface, administrators and folder managers can manage this shared template library. That right does not grant access to processes outside their managed folders. Request cleanup starts with a preview; actual deletion requires an explicit deletion request.

[ASP.NET](http://ASP.NET) code in built-in or custom forms runs on the WorkflowGen server. Have the code and access rules reviewed by your administrator before publishing. Changing a process state does not remove a page that has already been published.

## Follow progress in WorkflowGen

**Follow changes as they are saved:** The skill guides your assistant to open the relevant WorkflowGen Administration or User Portal page and show meaningful progress throughout the work. It prefers an integrated browser panel on the right when your client supports one; otherwise it uses an available external browser. Automatic opening, control and refresh depend on the client’s browser tools and a signed-in WorkflowGen browser session, configured separately from the MCP connection. If browser control is unavailable, the assistant explains this and reports progress in the conversation.

**Avoid overwriting changes:** Use one active designer at a time. When browser control is available, the assistant refreshes the view it controls after saved changes. If another Designer tab for the same process version was already open before the assistant’s changes, preserve any unsaved input, then reload it before editing or saving there. Saving from an outdated tab can overwrite the assistant’s changes.

**When testing:** Agree with the assistant on the scenarios, test environment and account to use. MCP tools can create requests, supply test data and complete workflow steps that the connected account is authorized to perform. Those calls do not submit the browser form or test its client-side code and form validations. When browser control is available and authorized, the assistant can also fill and submit the actual forms and show request progress and test results. Starting or completing requests can trigger configured notifications, automatic actions and integrations.

The connected MCP server supplies WorkflowGen data and operations. Keep process work on the selected connection. Investigating local source code is a separate task; if an operation fails, report the server response and what was saved without assuming a local project matches the remote deployment.
