Ground your AI in verified Webix code,
not training data.

Paste your mcp_user token here

The token is stored only in this browser tab's sessionStorage. It is injected into the mcp.json snippet on step 3 in the browser — nothing is sent over the network.

No token set — step 3 will show a <paste-the-mcp_user-key-from-step-1> placeholder.

Add the webix entry to Cursor's mcp.json

Cursor reads MCP server registrations from one of two locations — the project-level file wins when both exist. Use the global file unless you want webix-mcp visible in only one project.

If mcp.json does not exist yet, save the file below as-is. If it already contains other MCP servers, merge the webix entry into the existing mcpServers object — do not overwrite the file.

PowerShell — create the directory if missing and open the file

New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\.cursor" | Out-Null
notepad "$env:USERPROFILE\.cursor\mcp.json"

bash — same on macOS / Linux

mkdir -p ~/.cursor
$EDITOR ~/.cursor/mcp.json   # or: nano ~/.cursor/mcp.json

Restart Cursor and check the MCP panel

Cursor only loads MCP servers at startup. A window reload (Ctrl+Shift+P → Reload Window) is not enough for new server registrations — do a full File → Exit, then reopen Cursor.

Where the MCP panel lives

It is not in the VS Code-style settings (Ctrl+,) — those are just the inherited editor settings. MCP servers are managed in the separate Cursor Settings window. Open it via any of:

• Command Palette: Ctrl+Shift+P → type Cursor Settings → pick Cursor Settings: Open Cursor Settings.
• Keyboard shortcut: Ctrl+Shift+J.
• Top-right gear icon → Cursor Settings (not just “Settings”).

Inside Cursor Settings, click Tools & MCPs in the left sidebar (under the Plugins group). Older builds may name it MCP, MCP & Integrations, or expose it under Features → Model Context Protocol.

What you should see

• Under Installed MCP Servers, an entry named webix.
• A green dot next to its name (red = handshake failed; click Show Output to see the stderr).
• The toggle on the right is on (Cursor disables servers that fail to connect).
• Expanding the entry lists 19 tools: the eight Webix tools (search_webix_snippets, get_snippet, list_webix_tags, list_webix_components, search_webix_docs, get_doc_page, list_webix_owners, get_webix_api_reference), three Proto-UI tools (search_softcreator_extensions, get_softcreator_extension, list_softcreator_extensions), and eight SC-pages tools (search_softcreator_pages, get_softcreator_page, list_softcreator_pages, search_page_components, get_page_component, get_control_properties, list_control_types, search_control_properties).

If the indicator is red

Click Show Output next to the entry — the line that matters is the one above the OAuth-fallback noise. Match it against this table:

Install the /webix slash command (recommended)

The slash command primes the agent with SoftCreator-specific guidance: the SC ↔ Webix name mapping, search strategy, and citation rules. Without it, the agent still has access to all 11 MCP tools — but it will not know to translate scdatatable ↔ ui.datatable, or to cite snippet URLs.

Save the file below as webix.md in the commands directory. No token is needed — the slash command is a pure prompt.

---
description: Find and adapt a SoftCreator/Webix snippet from the local knowledge base
---

You are working inside a SoftCreator project. SoftCreator extends Webix UI controls via Proto-UI; the canonical control names in this codebase are SC-prefixed: `scdatatable`, `scform`, `sclayout`, `sctree`, `sctreetable`, `sctext`, `scbutton`, etc.

You have access to the `webix-snippets` MCP server with nineteen tools spanning four domains.

**Webix snippets (post-processed: SC names applied where a wrapper exists):**
- `search_webix_snippets(query, tag, component, limit)` — full-text search. Use SC component names in the `component` filter (e.g. `component="scdatatable"`).
- `get_snippet(url)` — full JS+HTML by short URL id.
- `list_webix_tags(filter)` / `list_webix_components(filter, min_freq)` — discovery.

**Webix documentation (full local mirror of docs.webix.com):**
- `search_webix_docs(query, kind, owner, member_kind, limit)` — `owner` uses base Webix names (e.g. `ui.datatable`, NOT `scdatatable`).
- `get_doc_page(file_name)`, `list_webix_owners(...)`, `get_webix_api_reference(owner)` — the API reference also lists any SC extension that wraps a given Webix view.

**SoftCreator Proto-UI catalog:**
- `search_softcreator_extensions(query, primary_base, has_mixin, only_standalone, limit)` — search the SC catalog (35 wrappers + 24 standalone controls including codeeditor, bpmneditor, sctimeline).
- `get_softcreator_extension(name)` — full members, defaults, mixins, source code.
- `list_softcreator_extensions(filter, base_filter, only_standalone)` — discovery.

**SoftCreator UI pages (377 production pages, 4 237 deduplicated sub-tree patterns, 96 control-property schemas):**
- `search_softcreator_pages(query, domain_module, ui_pattern, primary_entity, feature, limit)` — full-text search. Each page carries a semantic analysis (purpose, primary entity, operations, features, UI pattern). Use this when the user wants a complete page composition to clone.
- `get_softcreator_page(page_id, include_config)` — full Webix UI config + analysis. Set `include_config=false` for metadata only; `true` (default) for the cloneable config.
- `list_softcreator_pages(domain_module, ui_pattern, primary_entity, name_filter, ...)` — directory by module / pattern / entity.
- `search_page_components(root_view, level, min_count, limit)` — find canonical sub-tree patterns. Each carries a count, n_distinct_pages, and a canonical example to copy.
- `get_page_component(fingerprint)` — canonical example + back-references to every page that shares the same shape.
- `get_control_properties(element_id)` — full property schema (name/label/view/tab/required/hidden) for one SC control type.
- `list_control_types(min_fields)` — enumerate the 96 harvested control types.
- `search_control_properties(query, view, required, limit)` — which controls expose a given property name or label.

**Workflow:**

1. Decide what the user needs:
   - **A complete page composition to clone** (e.g. "build a grid+form for entity X like in module Y") → start with `search_softcreator_pages`. Then `get_softcreator_page(...,include_config=true)` for the 1–2 best matches and adapt.
   - **A standalone sub-tree pattern** (e.g. "I want the standard SC Save button", "give me the canonical accordion+treetable") → `search_page_components` with the relevant `root_view`. Then `get_page_component(fingerprint)` for the canonical example and source references.
   - **A working code example for a single concept** → `search_webix_snippets`. The returned JS already uses SC names where applicable.
   - **The exact API of a Webix view** → `search_webix_docs` or `get_webix_api_reference(owner='ui.<name>')`. Docs use base Webix names.
   - **A SC-specific control or property** (Proto-UI defaults, mixins, custom methods) → `search_softcreator_extensions` / `get_softcreator_extension`. For property discovery, also `search_control_properties` (which controls accept gravity / minWidth / scroll / …).

2. When the user names a control in SC form (`scdatatable`, `sctree`, etc.) or in Webix form, translate:
   - For snippet/component search: pass the SC name as `component` / `root_view`.
   - For doc search: strip the `sc` prefix and pass `owner='ui.<base>'`.
   - For SC catalog and pages: pass the SC name directly.

3. For non-trivial requests, combine sources: page-level retrieval for the overall composition, snippets and component patterns for sub-trees, docs/extensions for property-level verification. Verify any unusual property against the docs (Webix base) AND the SC defaults (DataSourceID, optionsDataSource, linkedParentPageElementID, etc.) AND the harvested control properties.

4. After ranked results, fetch full content for the 1–2 best matches (`get_softcreator_page`, `get_page_component`, `get_snippet`, `get_doc_page`, `get_softcreator_extension`).

5. Produce a single working code block, in SC style (using SC view names where wrappers exist, Webix names otherwise).
   - Stay within the documented API surface — do not invent properties.
   - Reuse SC defaults when the task involves data binding.

6. After the code block, list your sources:
   - SC pages: `page_id` with module + UI pattern.
   - SC component patterns: `fingerprint` + canonical `page_id`:`path`.
   - Webix snippets: `https://snippet.webix.com/<url>`.
   - Docs: `https://docs.webix.com/<file_name>`.
   - SC extensions: name + primary_base.

7. If nothing relevant is found, say so explicitly and ask for clarification — do not fabricate code from memory.

User task:
$ARGUMENTS

PowerShell — create the directory and download the file in one go

New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\.cursor\commands" | Out-Null
# Save the file from this page using the "Download webix.md" button above,
# then move it into the commands directory:
Move-Item "$HOME\Downloads\webix.md" "$env:USERPROFILE\.cursor\commands\webix.md" -Force

bash — same on macOS / Linux

mkdir -p ~/.cursor/commands
mv ~/Downloads/webix.md ~/.cursor/commands/webix.md

After copying the file, reload the Cursor window: Ctrl+Shift+P → Developer: Reload Window. A full restart is not required for slash commands.

Try the /webix command in Cursor chat

Open the chat panel with Ctrl+L, switch the dropdown to Agent (MCP tools are only callable in Agent mode), and type one of the prompts below. The agent will call search_webix_snippets, search_webix_docs, and search_softcreator_extensions as needed, then return adapted SC code with citations to the original sources.

/webix datatable with frozen columns and pagination
/webix scdatatable defaults — what's DataSourceID for?
/webix codeeditor with Monaco — basic config
/webix list all events of ui.kanban
/webix bpmneditor wired into a SoftCreator layout

Drop webix.md into Claude Code's commands folder

Claude Code supports custom slash commands as plain Markdown files with YAML frontmatter — the exact same format Cursor uses. The file you saved in step 5 of the Cursor setup works unchanged; you just need a copy in Claude Code's commands directory.

Easiest path: copy the file you already saved for Cursor.

PowerShell

New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\.claude\commands" | Out-Null
Copy-Item "$env:USERPROFILE\.cursor\commands\webix.md" `
          "$env:USERPROFILE\.claude\commands\webix.md" -Force

bash — same on macOS / Linux

mkdir -p ~/.claude/commands
cp ~/.cursor/commands/webix.md ~/.claude/commands/webix.md

If you skipped the Cursor setup, grab the file from step 5 above — the body of the prompt is identical for both clients.

Run /webix in the Claude Code chat

Open the extension panel (Ctrl+Esc in Cursor), then type /webix followed by your question. Claude Code injects the prompt body, calls the webix MCP server's tools, and returns SC-shaped code with citations — the same workflow as Cursor's native agent.

/webix datatable with frozen columns and pagination
/webix scdatatable defaults — what's DataSourceID for?
/webix codeeditor with Monaco — basic config

To inspect MCP state from inside the chat, type the built-in command:

/mcp

It lists every connected server and the tools it exposes. Click the webix row to drill into its detail card — Reconnect, Clear authentication, Disable, and View tools. Expanding the tool list reveals the same nineteen tools the Cursor agent has access to.