Use GemBoss from Claude's connector directory
Connect GemBoss from Claude's directory, and what its 55 tools can and cannot do for your store.
The GemBoss connector in Claude's directory gives Claude 55 tools on the GemBoss stores you choose. Claude can build and revise landing pages, read your products and analytics, and check a page before a person publishes it. Nothing goes live from a chat.
What you need
A GemBoss account, which you can create while connecting, and your Shopify store connected to it in GemBoss under Settings → Connectors. Without a connected store Claude can still research your niche and draft pages, but a page has no product to sell and no product photos until the store is connected.
Connect
- In Claude, open Settings → Connectors, find GemBoss and choose Connect. Until the listing appears, add a custom connector with the URL
https://mcp.gemboss.ai/directory/mcp. - Claude opens the GemBoss sign-in. Sign in, or choose Create an account. An account you create here can be used straight away.
- Tick the stores Claude may work on and approve. What Claude may change in each store follows your role there: a role that can only view gives Claude reads only.
The connector shows as Connected, and its tools are available in any chat. Claude receives a token for the stores you ticked, never your password.
What Claude can do with it
| Job | Tools |
|---|---|
| Build a landing page from a brief | start_page_build, read_page_build_reference, check_page_build, finish_page_build, get_page_build |
| Revise a saved page | update_page_from_elements, set_page_copy, undo_page_change, list_page_history, get_page_recovery, element_vocabulary, archive_page, restore_page |
| Check a page and hand it over | verify_page, preview_page, request_page_publish, withdraw_page_publish, get_page_publication |
| Follow a funnel and its tests | check_funnel, get_funnel_build, list_campaigns |
| Read your store | get_shop, get_catalog, get_product, get_brand_kit, propose_brand_kit, list_pages, get_page, get_store_state |
| Measure | get_metrics, get_segment_funnel, get_device_metrics, get_source_metrics, get_visitor_metrics, get_time_patterns, get_campaign_revenue, get_creator_metrics, get_page_performance, rank_pages_to_fix, get_recommendations, get_tracking_health, get_ga_traffic, get_search_performance, get_behavior_signals, list_recordings, get_recording_moments, read_heatmap_image |
| Research a niche | get_niche_brief, get_page_anatomy, get_winning_brief, list_market_references, save_market_reference, get_reference_ads, get_store_dossier, list_section_recipes |
Every tool says in Claude whether it only reads or also changes something. The analytics tools read only. Google Analytics and Search Console numbers appear once you have connected them in GemBoss.
What it does not do
- Publish.
request_page_publishrecords a request with a preview link. A person publishes the page in GemBoss. - Delete. Archiving takes a page out of the working list, and restoring brings it back as a draft.
- Make images. This connector has no image generation. Pages use your products' photos and the pictures you add.
- Copy another site's page. A build starts from your brief. To set the layout,
read_page_build_referenceopens one scored reference page from GemBoss's library in a browser and measures its structure; your page gets your own words, products, prices and pictures.
Try it
- "List my GemBoss pages and tell me which one to fix first, and why."
- "Build a landing page for my best-selling product for cold traffic from Meta. Show me the preview link and do not publish."
- "Compare mobile and desktop conversion over the last 30 days and suggest one change."
Disconnect
In Claude, open Settings → Connectors → GemBoss and choose Disconnect. Claude stops reaching your stores. The pages it drafted stay in GemBoss as drafts.
Your data and what an AI assistant can see are covered in the privacy policy. For help, write to support@gemboss.ai.
Stuck on the connection?
You connect at https://mcp.gemboss.ai/mcp and sign in through your browser; there is no key to ask for. If the browser step does not finish, the troubleshooting page walks through what to check.
Thanks. That goes straight to the people who write these.