MCP for your website

The site's code only reads Blanxer, through the public API. Everything you change in the store while building (SEO text, products, photos, categories, coupons, delivery charges, the site link) you change through the Blanxer MCP, in your chat with the merchant. The site never holds a key and never calls the MCP (rule 6).

#Connect

The server is https://mcp.blanxer.com/mcp (streamable HTTP). The merchant signs in to Blanxer in the browser (OAuth). You never see a password or key, and you never ask for one.

Claude Code

claude mcp add --transport http blanxer https://mcp.blanxer.com/mcp

Or install the skill, which brings the MCP with it:

/plugin marketplace add blanxer-dev/blanxer-agent-skills
/plugin install blanxer-website@blanxer

Then run /mcp, pick blanxer and sign in.

Cursor: add to .cursor/mcp.json (project) or ~/.cursor/mcp.json:

{ "mcpServers": { "blanxer": { "url": "https://mcp.blanxer.com/mcp" } } }

Codex: add to ~/.codex/config.toml:

[mcp_servers.blanxer]
url = "https://mcp.blanxer.com/mcp"

Sign in when Codex asks (recent versions: codex mcp login blanxer).

claude.ai: Settings → Connectors → Add custom connector → URL https://mcp.blanxer.com/mcp.

The tools act as the person who signed in, with their role in the store. Most writes need the owner or a manager. If a tool says the role isn't allowed, ask the merchant to sign in as the owner.

#What you use it for

blanxer_how_to returns step-by-step guides for store tasks (SEO pass, editing products, and more). For the whole custom-site flow: blanxer_how_to { operation: 'custom_website' }.

With a website link saved, blanxer_audit_seo treats the custom site as the live site and reports <site>/sitemap.xml as the sitemap to submit.

#blanxer_set_storefront_url

blanxer_set_storefront_url { url: "https://mystore.com" }              // preview a save or change
blanxer_set_storefront_url { url: null }                               // preview clearing it
blanxer_set_storefront_url { dry_run: false, confirm_token: "..." }    // apply, after the merchant's yes

• Owner or manager.
• The first call saves nothing. It shows the old and the new value and returns a confirm_token. Show the merchant the change; after their yes, call again with { dry_run: false, confirm_token } only. If the link changed since the preview, the apply is refused; preview again.
• Blanxer cleans the link to https://<host>: it must be https, with no path, query, port or login, and not an IP or localhost. A bare mystore.com becomes https://mystore.com. A *.workers.dev link is fine. The MCP refuses *.blanxer.io and *.blanxer.com addresses (those are the Blanxer-hosted site).
• A save returns the product feed URL, the sitemap URL, and a reminder about the subdomain switch. Clearing returns only a confirmation (and a warning if the subdomain site is still hidden).

Once saved, Blanxer uses the site in:

• the tracking link it generates (dashboard copy, get_tracking_link);
• the confirmation emails of orders created in the dashboard, as leads or through Sambad (orders placed on the site use the site's own url);
• the delivered email;
• flash-sale alerts: the alert links to the url the site sent with "Notify me", which is kept only when it is on the store's domains, the saved link included;
• the product feed and the catalog sitemap.

Whether SMS short links follow it is not yet verified. Clearing the link puts these back on the custom domain if the store has one, else the subdomain (the delivered email falls back to <sub>.blanxer.com).

This tool ships with the BlanxerAPI release of the Blanxer MCP. Until your MCP lists it, the merchant pastes the link in the Blanxer dashboard → avatar menu → BlanxerAPI → Your website (rolling out).

#Confirm before bulk changes (rule 13)

Store data is live and shared with the dashboard, POS and mobile app. Before any change that touches many records (SEO for many products, imports, category renames, delivery charges):

1. Run the tool with dry_run: true where it has one, or list what will change.
2. Show the merchant the list or a sample, with counts.
3. Apply only after a clear yes.

The MCP's own confirmations still apply on top of this. Never invent product facts, reviews or claims in SEO text; use the product's own data and the merchant's words.

#What not to do

• Don't use the page-builder tools on a custom site (rule 12). These change the Blanxer-hosted site only:

  • blanxer_add_section, blanxer_update_section, blanxer_move_section, blanxer_remove_section, blanxer_duplicate_section
  • blanxer_apply_page_template, blanxer_create_page, blanxer_update_page, blanxer_duplicate_page, blanxer_delete_page
  • blanxer_update_navigation, blanxer_update_footer

  The custom site's design, menus and footer live in its code.

  Exception: blog post bodies. blanxer_create_blog_post makes an empty post; write its body with blanxer_add_section / blanxer_update_section using { post_id }. That is content the site shows (the post's sections), so use them for blog posts.

• Don't use the MCP from the site's code, and don't put an MCP token anywhere.

• Don't change store_visibility unless the merchant asks (see Deploy → Retiring the old subdomain site).

• Don't put product photos in the site's repo; upload them to Blanxer.