Connector — Model Context Protocol

Run the store's banners from your chat.

Protocol
MCP · Streamable HTTP
Endpoint
https://banners-mcp.awsgalaxy.com/mcp
Auth
OAuth 2.1 · WordPress login
Tools
10 · banner studio + manager
Status
running

This store exposes its Banner Studio and Banner Manager as a Model Context Protocol server, so an MCP client such as Claude can do everything the admin screens do — by conversation. Connect once over OAuth with your WordPress login; then resolve products from a pasted link or a plain description, generate a banner (or a short video), publish it to the product page, curate the homepage carousel, and push to the CRM — all from chat. It runs on the same AI sidecar that powers search and the on-site assistant.

§1Connect

One OAuth login from your MCP client.

Add the endpoint as a custom connector. The client discovers the authorization server, registers itself, and opens a consent page that signs you in with your WordPress username and an Application Password — no separate account, no API key to paste. Access is scoped to manage_woocommerce, and every action the connector takes runs as you.

  1. In your MCP client, add a custom connector and paste the endpoint https://banners-mcp.awsgalaxy.com/mcp
  2. It opens "Connect Sherry Banners" — sign in with your WordPress username + an Application Password (wp-admin → Users → Profile → Application Passwords).
  3. Authorize — the ten tools appear. Ask: "what banners are live, and which on-sale products have none yet?"
Endpoint
/mcp · Streamable HTTP
Authorize
OAuth 2.1 · DCR + PKCE
Identity
WordPress + Application Password
Scope
manage_woocommerce
Acts as
the logged-in operator
§2Tools

Everything the two admin screens do — as tools.

Paste one or many product links, titles, or a plain-language description; the server resolves them to real catalogue items. Generated and existing banners come back as inline images in the chat, so the whole make → publish → curate loop happens without opening wp-admin.

find_products
resolve URLs, titles, ids, or a description to products
generate_banner_image billed
compose a banner (1K–4K) for the product(s)
generate_banner_video billed
extend into a short promo video
publish_banner
put the image / video live on the product page(s)
set_carousel
curate the homepage carousel (replace / add / remove)
send_to_crm
ship a banner to a HubSpot landing page + Note
list_banners · banner_insights
what's live, what's in the carousel, on-sale items with no banner yet
remove_banner · check_generation_status
take a banner down · poll a long-running job
Resolve
link · title · id · NL — one or many
Preview
banners returned inline
Publish
product page · homepage carousel
Distribute
→ CRM hosted landing page
Backend
the store's own REST API
§3Safety

Nothing is spent, or changed, without you.

Image and video generation cost money, so those tools are gated: the first call returns a price estimate and a summary of exactly what it will make, and spends nothing until you confirm. Free actions — search, list, publish, carousel, send — run immediately. Your WordPress credential is held encrypted, bound to the session, and is never returned to the client; the store's internal API stays private behind the connector.

make the cheapest banner for these two and put only them in the carousel
2 × 1K ≈ $0.08 — generate? (nothing spent yet)
go
done — both live, carousel now shows exactly these two
Transcript — illustrative, no fixed script
Billed
estimate + confirm before spend
Free
search · list · publish · carousel · CRM
Credential
encrypted at rest · session-bound
Surface
only MCP + OAuth paths are public
Portable
any WooCommerce store · any MCP client
Connect it

Add the endpoint to your MCP client and sign in.

The same banners you create over chat publish straight to this live storefront — product pages and the homepage carousel.

MCP endpointhttps://banners-mcp.awsgalaxy.com/mcp
A live prototype by AWS GALAXY
Shopping Cart
Scroll to Top