WebsitePublisher.ai

WebsitePublisher.ai — Build and publish websites through AI conversation WebsitePublisher.ai is a remote MCP server that gives AI assistants the power to…

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • List Projects: List all projects the authenticated user has access to
  • Get Project Status: Get detailed status of a specific project including page, asset, and entity counts
  • List Pages: List all pages in a project

What data it sees

Do you need an account

No: the server works without sign-in

WebsitePublisher.ai — Build and publish websites through AI conversation WebsitePublisher.ai is a remote MCP server that gives AI assistants the power to create, manage and publish complete websites. No local installation required — connect via OAuth 2.1 and start building. 27 tools across 5 API domains:

Pages — Create, edit and publish HTML pages with full asset management Assets — Upload images, CSS, JavaScript and other files Entities & Records — Structured data storage for dynamic content Integrations — Connect external services like Stripe, Mailgun, SendGrid Project Management — Create projects, manage settings, custom domains

Key features:

Remote server — nothing to install OAuth 2.1 with auto-discovery (RFC 9728) Streamable HTTP transport Works with Claude, ChatGPT, Mistral/Le Chat, Cursor and more Free tier available, paid plans from €9/month

Get started: Connect your AI assistant to https://mcp.websitepublisher.ai/ — OAuth handles the rest automatically. 📖 Docs: https://websitepublisher.ai/docs 💻 GitHub: https://github.com/megberts/mcp-websitepublisher-ai

How to connect

How to connect WebsitePublisher.ai to Claude

The server address to paste into Claude settings:

https://mcp-websitepublisher-ai.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect WebsitePublisher.ai to ChatGPT

The server address to paste into ChatGPT settings:

https://mcp-websitepublisher-ai.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect WebsitePublisher.ai to Cursor

The server address to paste into Cursor settings:

https://mcp-websitepublisher-ai.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (30)

Raw names from tools/list. Only developers need these.

list_projectsList all projects the authenticated user has access to
get_project_statusGet detailed status of a specific project including page, asset, and entity counts
list_pagesList all pages in a project
get_pageGet a specific page with its content. Returns version and version_hash for use with patch_page.
create_pageCreate a new page with HTML content
update_pageReplace an existing page with full new content. For small changes, use patch_page instead — it saves tokens and preserves version history.
delete_pageDelete a page
patch_pageApply targeted changes to an existing page without sending the full content. Requires base_version_hash from get_page to prevent conflicts. Supports replace and delete operations. Much more efficient than update_page for small edits.
get_page_versionsGet the version history of a page. Returns metadata (version numbers, hashes, timestamps, change summaries) — no content. Useful to check what changed or find a version to rollback to.
rollback_pageRollback a page to a previous version. Creates a new version with the old content (audit trail preserved). Specify either target_version (number) or target_version_hash. Use get_page_versions to find available versions.
list_assetsList all assets (images, CSS, JS, etc.) in a project
upload_assetUpload an asset (image, CSS, JS, etc.)
delete_assetDelete an asset
list_entitiesList all entities (data models) in a project. Entities are like database tables that store structured data.
create_entityCreate a new entity (data model). Example: create a "blogpost" entity with title, content, author fields.
get_entity_schemaGet the schema definition of an entity, including all its properties and their types
delete_entityDelete an entity and ALL its data. This action cannot be undone!
update_entityUpdate entity metadata such as plural name, description, or public_read access. Set public_read to true to make entity data accessible without authentication via /mapi/public/{projectId}/{entity}.
list_recordsList all records of an entity type with optional pagination
get_recordGet a single record by ID
create_recordCreate a new record in an entity. Fields depend on the entity schema.
update_recordUpdate an existing record. Only provided fields will be updated.
delete_recordDelete a record by ID
vault_list_secretsList all secrets stored in a project's vault. Returns metadata only (key names, prefixes, service types, status) — never the actual secret values. Use this to check what credentials are stored before setting up integrations.
vault_store_secretStore or update a secret in the project vault. The value is encrypted with AES-256-GCM and can never be read back. Use this to save API keys for integrations. If the key_name already exists, the value is replaced. For integration setup, prefer setup_integration which handles validation.
vault_delete_secretPermanently delete a secret from the project vault. This cannot be undone. The encrypted value is destroyed.
list_integrationsList all available integrations and their configuration status for a project. Shows which integrations are fully configured (vault secrets present and ready to use) and which are available but need setup. Each integration includes its available endpoints.
setup_integrationConfigure an integration by storing its required API keys in the vault. Validates key format against the integration manifest. After setup, the integration endpoints become available for execute_integration calls. Use list_integrations first to see what secrets are required.
execute_integrationExecute an integration action — e.g., send an email via Resend, create a payment via Mollie. The system resolves vault credentials server-side so you never handle API keys directly. The integration must be configured first via setup_integration. Input fields depend on the specific endpoint (use list_integrations to see available endpoints and their schemas).
remove_integrationRemove an integration by permanently deleting all its vault secrets. After removal, the integration endpoints will no longer work until reconfigured via setup_integration.