ChatGPT Plugin

PageRush: Instant websites

Websites for everyday people

Brand: PageRush

Category: Pending
Primary Subcategory: Pending

Integration details

Description

The website builder for everyday people. PageRush websites are highly performant and SEO-friendly by design. PageRush is a text-based website builder, not an AI website generator. It turns formatted text into live websites and renders it deterministically through supported landing-page and blog elements. PageRush takes care of layout, hosting, performance, and technical details, so you can focus on the content. It lets you create, publish, and manage landing pages and articles directly from ChatGPT. ChatGPT users can publish their most recent page for free, allowing for a full experience right away.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: PageRush
Access: Account required
First tracked: 2026-10-17
Tool count: 37
Geography: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce PageRush: Instant websites has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

37 tools agents can invoke

Use this after create_post_prompt when creating a brand-new PageRush post or landing page from full MDX content. PageRush content is text-based MDX/Markdown plus the supported PageRush components inside that content; do not treat this as arbitrary UI or code generation. For landing pages, sales pages, institutional pages, campaigns, or home pages, include mode:"landing-page" in the MDX frontmatter. For articles, guides, or blog posts, include mode:"blog-post". Do not use to edit an existing post.
create_post
Use this when the user wants to permanently delete a PageRush image by imageId. If the image is still used in posts, deletion is blocked and the result returns the image plus affected posts so you can ask whether to remove the image from those posts before retrying deletion. Do not use for hiding or unselecting an image.
delete_image
Use this when the user wants to permanently delete a PageRush post. Prefer slug in user-facing references; postId is only a compatibility fallback. Do not use for drafts that should merely be unpublished.
delete_post
Use this after edit_post_prompt and get_post_content when saving full MDX edits to an existing PageRush post. Before saving, PageRush creates a temporary restore point for the previous post MDX and publish state; the user can restore the previous version for 1 hour with restore_pagerush_change. This is a recoverable public-site edit: PageRush saves the previous MDX and publish state first, and published posts can affect the live website. PageRush content is text-based MDX/Markdown plus the supported PageRush components inside that content; do not treat this as arbitrary UI or code editing. Prefer slug in user-facing references; postId is only a compatibility fallback. Do not use for new posts; use create_post.
edit_post
Use this after edit_privacy_policy_page_prompt and get_privacy_policy_page_content when saving the PageRush Privacy Policy page content shown at /privacy and linked from the website footer. Before saving, PageRush creates a temporary restore point for the previous legal page text; the user can restore the previous version for 1 hour with restore_pagerush_change. This is a recoverable public-site edit: PageRush saves the previous page text first, and the saved page is public. Input must be Markdown text only. Do not include frontmatter, MDX components, JSX, HTML, imports, exports, scripts, styles, or code. Recommend starting with "# Privacy Policy". Do not use for posts, categories, site settings, or images.
edit_privacy_policy_page
Use this after edit_site_settings_prompt and get_site_settings when saving PageRush site settings. For normal edits, pass siteSettingsPatchJson with only the changed settings fields; use siteSettingsJson only when a whole settings-document replacement is necessary. Before saving, PageRush creates a temporary restore point for the previous site settings; the user can restore the previous version for 1 hour with restore_pagerush_change. This is a recoverable public-site edit: PageRush saves the previous settings first, and the change can affect the live website. PageRush does not support arbitrary UI or code customization here; this is primarily for text-based site metadata and the single primary site color. Use siteTitle for the short visible header title/logo text and siteName for the SEO/social brand name. If the color changes, call show_color_preview after saving so the user can see the hex color. If editing WhatsApp CTA settings, explain it uses a signature design by Carlos Alegre, the PageRush creator: bottom-center, wide, thumb-friendly on mobile, visually prominent, and shown on post pages after scroll. Do not use for post MDX, legal pages, images, or nickname changes.
edit_site_settings
Use this after edit_terms_of_service_page_prompt and get_terms_of_service_page_content when saving the PageRush Terms of Service page content shown at /terms and linked from the website footer. Before saving, PageRush creates a temporary restore point for the previous legal page text; the user can restore the previous version for 1 hour with restore_pagerush_change. This is a recoverable public-site edit: PageRush saves the previous page text first, and the saved page is public. Input must be Markdown text only. Do not include frontmatter, MDX components, JSX, HTML, imports, exports, scripts, styles, or code. Recommend starting with "# Terms of Service". Do not use for posts, categories, site settings, or images.
edit_terms_of_service_page
Use this when the user asks which PageRush features are available for their account, whether custom domains, marketing pixels, WhatsApp CTA, or unlimited live posts/pages are available, or why only one published post is live. This returns current account feature access and the official PageRush domain for learning more. Do not create checkout, return billing URLs, or present ChatGPT as a purchase path.
get_account_feature_access
Use this to identify the PageRush account represented by the authenticated connection. The opaque profile ID remains stable across reconnection and changes to email or nickname.
get_profile
Use this when the user selected or provided a PageRush image ID and needs its URL and alt text. In PageRush, an image is used either as a post cover image, including the featured post shown as the homepage hero, or as a Markdown/MDX image inside the post body. Cover images are the main image shown first for a post or page, including the featured post shown as the homepage hero. PageRush follows a common internet/web standard for cover images: they are shown in a responsive landscape 16:9 frame. Vertical images are center-cropped there. When talking to the user, say "cover image", not "frontmatter". If framing matters, recommend cropping or editing the image in their device gallery or another image editor before uploading it to PageRush. Do not describe it as a custom hero, banner, background, or generic site-builder asset. Do not use to list images.
get_image
Use this when you need to identify the logged-in PageRush website owner, bootstrap the session, check whether the permanent nickname is set, or get the public website URL. This is the recommended first tool for PageRush MCP conversations. PageRush is a hosted text-based website builder, not a custom UI/code editor. When explaining that to the user, keep it positive and non-technical: describe it as a content-first website builder shaped by the content on each page. The website only goes live and gets public URLs after nickname setup. The nickname controls the public website URL/subdomain only; the site name belongs in site settings. Do not use to set or change the nickname.
get_user_nickname_and_website_url
Use this after edit_post_prompt when the user wants to edit an existing PageRush post. Returns the current full MDX once, without editing instructions. Do not use this when the user only wants to see or read a post; use get_post_for_reading for read-only requests. Do not use for creating brand-new posts.
get_post_content
Use this before creating a brand-new PageRush post or landing page. Returns the PageRush MDX creation instructions only; after reading it, write the complete MDX and call create_post. PageRush is a text-based website builder, not a no-code UI builder or arbitrary code generator.
create_post_prompt
Use this before editing an existing PageRush post. Returns the PageRush MDX edit instructions only, without the current post content; after reading it, call get_post_content, then call edit_post with the full updated MDX. PageRush is a text-based website builder, not a no-code UI builder or arbitrary code editor.
edit_post_prompt
Use this when the user wants to see, read, or inspect an existing PageRush post without editing it. This is the default reading tool. For published posts, return the public URL first. For drafts, rawContent always contains the complete MDX, including frontmatter and body. Use it to present the draft naturally as readable page content without showing literal MDX or calling it source. If the user explicitly asks for the source text, set includeRawContent true; only then show rawContent in an mdx code block. Do not use this tool for editing; use edit_post_prompt and get_post_content only when an edit will follow.
get_post_for_reading
Use this after edit_privacy_policy_page_prompt when the user wants to read or edit the PageRush Privacy Policy page shown at /privacy and linked from the website footer. Returns the current Markdown text only, without editing instructions. This is Markdown text for a legal page, not post MDX and not site-settings JSON. Do not use for posts, categories, site settings, or images.
get_privacy_policy_page_content
Use this before editing the PageRush Privacy Policy page. Returns Markdown editing instructions and small website context only; after reading it, call get_privacy_policy_page_content for the current text, then call edit_privacy_policy_page with the full updated Markdown text.
edit_privacy_policy_page_prompt
Use this when the user wants the public URL for a published PageRush post. Prefer slug in user-facing references; postId is only a compatibility fallback. Do not use for drafts.
get_post_url
Use this when the user needs a quick list of their 3 most recently updated PageRush posts. Refer to posts by slug or title in user-facing language. Do not use when cleanup requires more than 3 posts; use list_all_posts_for_management.
get_recent_posts
Use this when the user wants public URLs for up to 3 most recent published PageRush posts after nickname setup. Do not use before the permanent nickname is set, for drafts, or for management cleanup.
get_most_recent_posts
Use this when the user asks what color is currently set on the PageRush website. PageRush exposes only one primary site color through MCP. Do not use this tool for general site settings edits; use edit_site_settings_prompt, get_site_settings, or edit_site_settings for that. If the user wants to see or compare the color visually, call show_color_preview next.
get_site_color
Use this after edit_site_settings_prompt when the user wants to inspect or edit PageRush site settings as JSON. Returns the current JSON only, without editing instructions. For normal edits, compare the current JSON to the requested change and call edit_site_settings with siteSettingsPatchJson containing only changed fields. PageRush does not support arbitrary UI or code customization here; site settings mainly control text-based site metadata and the single primary site color. Use siteTitle for the short visible header title/logo text and siteName for the SEO/social brand name. Do not use for post content, legal pages, images, or nickname changes.
get_site_settings
Use this before editing PageRush site settings. Returns JSON editing instructions only; after reading it, call get_site_settings for the current JSON, then call edit_site_settings with siteSettingsPatchJson containing only changed fields. Use a full siteSettingsJson replacement only when necessary. Do not use for post MDX, legal pages, images, or nickname changes.
edit_site_settings_prompt
Use this after edit_terms_of_service_page_prompt when the user wants to read or edit the PageRush Terms of Service page shown at /terms and linked from the website footer. Returns the current Markdown text only, without editing instructions. This is Markdown text for a legal page, not post MDX and not site-settings JSON. Do not use for posts, categories, site settings, or images.
get_terms_of_service_page_content
Use this before editing the PageRush Terms of Service page. Returns Markdown editing instructions and small website context only; after reading it, call get_terms_of_service_page_content for the current text, then call edit_terms_of_service_page with the full updated Markdown text.
edit_terms_of_service_page_prompt
Use this when the user wants their PageRush website URL as plain text after nickname setup. Do not use before the permanent nickname is set or for individual post URLs. The returned websiteUrl is always the real tenant URL, such as a subdomain or custom domain; do not invent path-style nickname URLs.
get_website_url
Use this when managing, cleaning up, publishing, editing, featuring, or deleting PageRush posts and more than the 3 most recent posts may matter. Refer to posts by slug or title in user-facing language. Do not use for public visitor-facing post URLs.
list_all_posts_for_management
Use this when the user wants to browse PageRush images, open the user's image gallery, select an existing image, or delete an unused image. The inline widget is a compact image-gallery launcher; the user presses Open image gallery to browse, select, preview, or delete images in fullscreen. In PageRush, an image is used either as a post cover image, including the featured post shown as the homepage hero, or as a Markdown/MDX image inside the post body. Cover images are the main image shown first for a post or page, including the featured post shown as the homepage hero. PageRush follows a common internet/web standard for cover images: they are shown in a responsive landscape 16:9 frame. Vertical images are center-cropped there. When talking to the user, say "cover image", not "frontmatter". If framing matters, recommend cropping or editing the image in their device gallery or another image editor before uploading it to PageRush. Do not describe it as a custom hero, banner, background, or generic site-builder asset. Do not use this tool only to explain cover image framing, aspect ratio, cropping, vertical images, or unsupported custom cover-image positioning; answer those cases in text unless the user is actually browsing, selecting, or deleting existing PageRush images. Do not use for uploading new images; use show_image_upload_on_screen for local/private uploads or upload_image_from_url when a public URL is already known. Do not send the user to the PageRush dashboard for normal image-library management that this widget already supports.
show_images_manager
Use this when the user needs to upload one new PageRush image from their device. Upload one image at a time; bulk upload is not supported. A chat attachment cannot be uploaded; for local image files, use show_image_upload_on_screen instead. The widget accepts PNG, JPEG, WebP, and GIF images up to 3 MB. Image links that start with https://, including GIF links, are allowed through upload_image_from_url up to 3 MB. If a local image is over 3 MB, say it is too large for the ChatGPT upload widget and the user can upload it in the main PageRush app instead. In PageRush, an image is used either as a post cover image, including the featured post shown as the homepage hero, or as a Markdown/MDX image inside the post body. Cover images are the main image shown first for a post or page, including the featured post shown as the homepage hero. PageRush follows a common internet/web standard for cover images: they are shown in a responsive landscape 16:9 frame. Vertical images are center-cropped there. When talking to the user, say "cover image", not "frontmatter". If framing matters, recommend cropping or editing the image in their device gallery or another image editor before uploading it to PageRush. Do not describe it as a custom hero, banner, background, or generic site-builder asset. Do not use this tool only to explain cover image framing, aspect ratio, cropping, vertical images, or unsupported custom cover-image positioning; answer those cases in text unless the user is actually uploading a new image. Do not use when the assistant already has an image link that starts with https://; call upload_image_from_url directly. Do not send the user to the PageRush dashboard for image upload when this widget can handle it.
show_image_upload_on_screen
Use this immediately when the user asks to create or start a PageRush website and the current context shows that no permanent nickname is set. Open the guided UI instead of suggesting nicknames in chat. Nicknames cannot be changed after setup. The nickname controls the public website URL/subdomain only; the site name belongs in site settings. After saving, continue the user's original website request when it is available in the conversation context; otherwise, ask what they want to create or do next in PageRush. Do not use if the profile already has a nickname.
nickname_setup
Use this when the user wants to publish a draft post or move a published post back to draft. Prefer slug in user-facing references; postId is only a compatibility fallback. Do not use to edit post content.
set_post_as_published_or_draft
Use this when the user asks to undo or restore a recent PageRush MCP edit and provides a restoreToken returned by an edit tool. Restores a recent PageRush edit using a temporary restore point created automatically before the edit was saved. Restore points are scoped to the authenticated user and expire after 1 hour. This is a recoverable public-site restore, not an irreversible delete/reset. The restore operation creates a new inverse restore point before applying the restore, so the restore can also be undone while that new token is valid.
restore_pagerush_change
Use this when the user wants a published PageRush post featured on their homepage. Prefer slug in user-facing references; postId is only a compatibility fallback. Do not use with draft posts.
set_post_as_featured_post
Use this when setting the authenticated PageRush user nickname for the first and only time. The user must have no nickname yet and explicitly choose a permanent public website nickname. Nicknames cannot be changed after setup. This controls the public PageRush URL/subdomain only. Do not call this to rename an existing website or to change the site name in settings. After saving, continue the user's original website request when it is available in the conversation context; otherwise, ask what they want to create or do next in PageRush. For a generic website-start request with missing identity details, ask concisely for the missing site or business name, purpose, main offering or audience, short description, and any desired contact or footer details.
set_nickname
Use this when the user asks to see, compare, confirm, or preview a PageRush site color hex code, especially after changing the single PageRush site color. This tool is preview-only. Do not use it to save settings; use edit_site_settings for changes.
show_color_preview
Use this when the user wants to import one image link that starts with https:// into their PageRush image library. Image links, including GIF links, are allowed up to 3 MB. Upload one image at a time; bulk upload is not supported. In PageRush, an image is used either as a post cover image, including the featured post shown as the homepage hero, or as a Markdown/MDX image inside the post body. Cover images are the main image shown first for a post or page, including the featured post shown as the homepage hero. PageRush follows a common internet/web standard for cover images: they are shown in a responsive landscape 16:9 frame. Vertical images are center-cropped there. When talking to the user, say "cover image", not "frontmatter". If framing matters, recommend cropping or editing the image in their device gallery or another image editor before uploading it to PageRush. Do not describe it as a custom hero, banner, background, or generic site-builder asset. After success, confirm that the image was imported and is ready to use without showing an image ID, storage path, or transfer details. If the user wants an image from the internet and has no URL, PageRush recommends searching Pexels for a high-quality free-to-use image matching their description, then importing that image link. If the current AI model cannot browse/search Pexels or extract a direct image link, tell the user the current AI model in use does not have that internet image-search capability and ask for an image link that starts with https:// or local upload. Do not use for local files, chat attachments, bulk uploads, or non-image URLs.
upload_image_from_url
Use this from the PageRush image upload widget when uploading a local GIF, or as the fallback local image uploader for one PNG, JPEG, WebP, or GIF file up to 3 MB. The user does not need the image ID, storage path, or transfer details; describe it simply as uploading an image to PageRush. In PageRush, an image is used either as a post cover image, including the featured post shown as the homepage hero, or as a Markdown/MDX image inside the post body. Cover images are the main image shown first for a post or page, including the featured post shown as the homepage hero. PageRush follows a common internet/web standard for cover images: they are shown in a responsive landscape 16:9 frame. Vertical images are center-cropped there. When talking to the user, say "cover image", not "frontmatter". If framing matters, recommend cropping or editing the image in their device gallery or another image editor before uploading it to PageRush. Do not describe it as a custom hero, banner, background, or generic site-builder asset. Do not call this for image links that start with https://; use upload_image_from_url instead.
upload_image_from_data_url

FAQs