VIXNODE

VIXNODE helps you create, edit, preview, and publish websites with AI. Manage projects and pages, generate or update content, work with images, review SEO settings, and publish changes online from your VIXNODE account. It supports single-page and multi-page websites across devices.

View in the ChatGPT registry

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Content & Design
Primary Subcategory: AI Website Builders
Secondary Subcategories: None listed
Brand: VIXNODE
Access: Account required
First tracked: 2026-06-02
Tool count: 22
Geography: US

ChatGPT Plugin Discoverability Score

ChatGPT organic discovery is not live yet

VIXNODE is tracked in the ChatGPT Plugin registry. Public organic-discovery measurement is not live for ChatGPT yet, so there is no score to publish today.

Get notified when your score goes live

Enter your work email and we’ll notify you when ChatGPT Plugin organic discovery scoring launches.

No spam. Unsubscribe any time.

Talk to our team

Primary Subcategory

Competing in ChatGPT AI Website Builders

View Category

Listed in alphabetical order

Primary Subcategory

B12 Website GeneratorOrganic discovery is pendingGet the score at launch

DazzlyOrganic discovery is pendingGet the score at launch

Grapes StudioOrganic discovery is pendingGet the score at launch

Insta Website BuilderOrganic discovery is pendingGet the score at launch

Instant WebsiteOrganic discovery is pendingGet the score at launch

VIXNODEOrganic discovery is pendingGet the score at launch

Score explained

How the Discoverability Score works

Organic discovery scoring for VIXNODE on ChatGPT is not live yet. The score will use measured agent conversations when it launches.

InvisibleBuriedEmergingCompetitiveWinning

Organic discovery scoring is pending. Your Plugin score will appear on this scale when measurement goes live.

FoundDiagnostic

Whether Claude found your Plugin in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.

PickedMain score

How often your Plugin appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.

PositionedDiagnostic

What position your Plugin appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.

Read the full scoring methodology Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.

Tools

22 tools agents can invoke

Compares a project page HTML version with its previous version and returns patch and both contents. Please provide a plain-language summary of changes first. If the user asks for programming details, then explain using code-focused technical terms.
get_project_page_html_compare_by_version
Create a new website project. If the user has not created any project yet, the assistant should ask whether to create one. Before creation, the assistant must confirm the project name with the user. This tool does not require UI confirmation. After a successful creation, call get_project_pages again with the returned project id.
create_project
Create a new web page under a specific project in VIXNODE. MANDATORY PRE-CALL CHECKLIST: Before invoking this tool, the assistant MUST have explicit user confirmation for: 1) Target project: say the project name and ask the user to confirm. Even if there is only one project, confirmation is still required. Do not auto-select a project even if the account has exactly one project. The assistant may suggest the only available project, but must wait for user confirmation before calling create_web_page. Do not display project_id or page_id to the user unless the user explicitly asks for those IDs. 2) Style source: ask whether to use A. uploaded image as style reference, B. a VIXNODE reference theme, or C. a custom style. Also tell the user that a style list UI can be shown for interactive style selection. When asking this, explicitly tell the user they can define custom style preferences (for example: color palette, typography, spacing, visual mood, component style, and reference sites). If the user chooses VIXNODE reference theme, call get_reference_themes first. If the user chooses uploaded image/custom style, summarize the interpreted style and ask for confirmation. If the user provides an image and asks to create a page based on it, treat the image as a proposed style source, not as final confirmation. The assistant must summarize the interpreted style and ask whether to proceed with that style. Before generating final HTML, the assistant should present the prompt summary and ask user confirmation. Prompt should use Markdown and plain-language content/style summary, and should not mention project name or project creation action. Preview confirmation generated by this tool does NOT replace the above checks. If HTML is truncated and cannot be previewed correctly, ask the user to try ChatGPT Work mode: https://chatgpt.com/?surface=work. Use mode='preview' to generate preview only. Use mode='create' for actual creation with confirmByUser=true and confirmToken. Input keys (only): project_id, name, page_id, pageType, layout, lang, public, fileName, html, prompt, mode, confirmByUser, confirmToken. Legacy key confirm is accepted for backward compatibility only. Do not use removed keys: selected_theme_id, selected_theme_name, themeConfirmed. Note: If the user does not mention programming details, respond in plain language. If the user mentions programming details, then respond with code-related content.
create_web_page
Retrieves all pages across all website projects for fast navigation and search. Invoke this MCP tool by name 'get_all_project_pages' directly (do not construct HTTP paths such as /VIXNODE/... ). In user-facing messages, show project/page names instead of project_id/page_id unless the user explicitly requests those IDs.
get_all_project_pages
Retrieves VIXNODE platform operation guides, including features, steps, and FAQ. Available doc ids: vixnode_mcp, create_website, custom_domain, invite_member, create_page, ai_vision_generate_page, ai_assistance_modify_node, ai_assistance_explain_node, ai_assistance_ask_node, ai_assistance_generate_node, ai_assistance_generate_image, filter_find_node, set_api_connection_data_source, setting_seo_metadata, view_restore_webpage_modification_history, manage_resource_files, manage_published_files.
get_docs
Retrieves one project image (or thumbnail) for MCP widgets without relying on browser direct /API/GetImage access.
get-image
Retrieves uploaded project images and displays a multi-select gallery. Default project_id is empty, and no gallery data is loaded until a project is selected. Before calling this tool with a non-global project_id, ask the user whether to open another project's gallery. After user selection and submit, selected image paths are sent back to the model for webpage content generation. If the user mentions photo gallery/image library, selecting images, or replacing/changing photos, call this tool.
get-photo-gallery
Retrieves the HTML design content of a specific page within a project. This is the HTML content of the page that has not been published.
get_project_page_html
Retrieves project page HTML content by version (commit sha).
get_project_page_html_by_version
Retrieves version history (sha and versionDateTime) of a specific project page HTML. To get the HTML content for a specific version, call the 'get_project_page_html_by_version' tool with the desired version.
get_project_page_html_history
Retrieves SEO settings for a specific project page, including SEO meta tags and SEO data structure. When links are provided in the result, always include and present all link fields in your reply (resource_link, published_link, validator_rich_results, markup_helper).
get_project_page_seo_setting
Retrieves a list of project pages along with their details (such as page name and URL). In user-facing messages, show project/page names instead of project_id/page_id unless the user explicitly requests those IDs.
get_project_pages
Retrieves the published HTML content of a specific page within a project.
get_published_page_html
Retrieves all reference themes. These themes define different categories, types, and color options that can be applied to the appearance and style of the site. When the user asks to change style/theme/look-and-feel/color palette/visual tone (for example: '改變風格', '換主題', '調整配色', 'make it more modern', 'switch to a minimal style'), call this tool first to get candidate themes before proposing or generating modifications.
get_reference_themes
Retrieves SEO data structure samples from seo_dataTypes.json. You can optionally provide a specific type value (for example: Article, FAQPage, Product) to return a single sample.
get_seo_data_structure_sample
Retrieves HTML content from a URL.
get_url_html
Retrieve information about a VIXNODE account, including email, display name, plan details, and quotas.
get_account_info
Retrieves a list of projects associated with the authenticated user's website. In user-facing messages, show project/page names instead of project_id/page_id unless the user explicitly requests those IDs.
get_website_projects
Modifies and publishes SEO settings for a specific VIXNODE page. Before invoking this tool, present the exact proposed SEO tags and JSON-LD structured data to the user and obtain explicit approval in the conversation. The preview UI is read-only and does not apply changes. Call this tool only after the user clearly asks to proceed. After completion, call get_project_page_seo_setting so the user can review the published result.
modify_project_page_seo_setting
Modify an existing web page under a specific project and publish the latest HTML content. IMPORTANT: Before regenerating the page HTML for any modification, ALWAYS call get_project_page_html first to fetch the latest live HTML of the page. Never generate new HTML from memory or a stale copy; always base your changes on the freshly fetched HTML to avoid overwriting updates made after the last call. Target confirmation rule: if the user does not clearly specify the modification target (for example which project/page/section/content to update), the assistant MUST ask for confirmation first and must not modify proactively. Do not display project_id or page_id to the user unless the user explicitly asks for those IDs. Theme/style rule: only when the user asks to change style, theme, color palette, layout, visual tone, or overall look-and-feel, the assistant MUST first call get_reference_themes or show suitable themes. Modification flow: 1. Call get_project_page_html to read the current HTML. 2. If the modification is about content only, apply changes to the fetched HTML and call this tool for preview/confirmation. 3. If the modification is about style/theme/layout/look-and-feel: show or retrieve reference themes first; wait for the user to select a theme; ask whether to apply the selected theme; only after confirmation, generate HTML aligned to that theme and call this tool. 4. The page is modified only after user confirmation in the UI. If HTML is truncated and cannot be previewed correctly, ask the user to try ChatGPT Work mode: https://chatgpt.com/?surface=work. Important theme mapping rule: if the user selected a theme id such as Style-16, that theme id is only a reference used to derive the final HTML/CSS. Do not submit theme_id, selected_theme_id, selected_theme_name, or themeConfirmed in the final modify call; the final call must submit the generated html/css through html instead. Input keys (only): project_id, page_id, name, fileName, public, pageType, layout, lang, html, confirm, confirmByUser, confirmToken. Do not use removed keys: selected_theme_id, selected_theme_name, themeConfirmed. Note: If the user does not mention programming details, respond in plain language. If the user mentions programming details, then respond with code-related content.
modify_web_page
Reconnect VIXNODE and choose a different account.
switch_account
Upload one image to the selected project photo library.
upload_image

VIXNODE FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are VIXNODE alternatives on ChatGPT?

As of 2026-08-14, VIXNODE competes with B12 Website Generator, Dazzly, Grapes Studio, Insta Website Builder, Instant Website, Instant Website, Jimdo, Laioutr, Pixelesq, Web on Demand Website Builder, WebsitePublisher, Wix in ChatGPT AI Website Builders, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.