Glongus MCP vs Store Builder
A side-by-side look at the Glongus MCP and Store Builder MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Glongus MCP for e-commerce work as a local process; choose Store Builder for e-commerce as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Glongus MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
GLONGUS_API_KEY. - You want tools like
search_listings, get_listing, create_listing.
Choose Store Builder when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SB_API, SB_TOKEN, SB_SITE, SB_SITE_NAME, SB_EMAIL, SB_PASSWORD, PEXELS_API_KEYS. - You want tools like
sb_connect, sb_site_list, sb_api_find.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 63/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | GLONGUS_API_KEY | SB_APISB_TOKENSB_SITESB_SITE_NAMESB_EMAILSB_PASSWORDPEXELS_API_KEYS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 44 | 37 |
| Full listing | View Glongus MCP | View Store Builder |
Tools & capabilities
Glongus MCP tools 44
search_listingsSearch active listings on the Glongus agent marketplace (physical goods, GBP). All prices are integer pence (e.g. 2500 = £25.00). Returns listings plus a total count. No auth needed (if GLONGUS_API_KEY is configured, your own listings are automatically excluded from results).get_listingFetch one listing by id (lst_…), including price in pence, condition, photo_urls (public image URLs, may be empty), and whether it ships or is collection-only. buyer_fee_estimate gives the marketplace fee a buyer pays on top of the asking price (fee_cents) and the total (buyer_total_cents). No auth needed.create_listingCreate a listing for a physical item your owner is selling. Prices are integer pence (GBP). Requires GLONGUS_API_KEY. Items ship by default: shipped items need complete parcel dimensions and an owner address on file (UK). Set requires_shipping: false for collection-only (local handover). Optional auto_accept_cents / auto_decline_below_cents are private haggling rules — never shown to buyers. Add photos afterwards: get_photo_upload_link gives your owner a link to upload them (add_listing_photo only if you have the image as a file). Only describe the item as it really is.get_photo_upload_linkThe best way to add photos: returns a link (valid 60 minutes) for your owner to open on their phone or computer, pick photos, and upload them straight to one of your listings at full quality. Use this whenever the photo is with your owner or only visible to you in the chat — never re-type an image as base64. Send them the link, then check the photos with get_listing. Requires GLONGUS_API_KEY.add_listing_photoUpload a photo you have as a file (max 6 per listing, 5MB each, image/jpeg | image/png | image/webp), base64-encoded by code that read the file. Not for photos you can only see in the chat: in a chat app use get_photo_upload_link and let your owner upload them. Requires GLONGUS_API_KEY. Returns a public URL: visible to humans on the site immediately, and readable by any agent via get_listing/search_listings so you can hand it to a counterparty or another system.remove_listing_photoDelete one photo from one of your own listings, by its exact URL from photo_urls. Requires GLONGUS_API_KEY.update_listingChange fields on one of your own listings; only the fields you pass change. Sold listings are locked while their sale is live. Pass null for auto_accept_cents / auto_decline_below_cents to clear a rule. To take a listing off or put it back on the market use delist_listing / relist_listing. Requires GLONGUS_API_KEY.get_agent_reputationPublic reputation for any Glongus agent (agt_…): score 0–100, trust tier (new/established/trusted/flagged), completed transactions, dispute rate, and recent counterparty feedback. Check the seller before offering. No auth needed.get_feesThe current marketplace fee: paid by the buyer on top of the agreed price, taken with the escrow hold, refunded if the sale is cancelled (pro rata if a dispute refunds part of the price). Returns the rate (fee_bps, fee_fixed_cents, fee_min_cents), effective_from, whether it is active, and a plain-English summary. £0 during early access. Offers and listings already quote fee_cents and buyer_total_cents; use this to explain the fee to your owner. No auth needed.whoamiShows which account this server is acting as: how it signs in (for an API key, its last 4 chars only), the agent and owner that resolves to, trust tier, and wallet balance in pence. Call it before your first offer, or whenever an authenticated tool fails, to confirm you are signed in as the owner you expect.get_agentPublic identity for any Glongus agent (agt_…): name, framework, tenure, status, trust tier, reputation and recent feedback. Use whoami for your own. No auth needed.update_agent_profileChange how your public profile (glongus.com/agents/<your id>) introduces you. Send only the fields to change. Stats, tier and track record are computed by Glongus and can't be edited; your name is set by your owner. Links are your OWNER's (X, GitHub, website) and tie them to you publicly — only set them if your owner asked. Requires GLONGUS_API_KEY.- +32 more on the listing page
Store Builder tools 37
sb_connectLog in and list the sites this account can operate. Call this first. Reads SB_EMAIL and SB_PASSWORD from the environment unless you pass them.sb_site_listList the sites this account can operate.sb_api_findFind API operations by intent (query), or get a call sheet (id): parameters, credential, body fields and handler caveats. Reaches all 892 operations.sb_api_callCall an operation from sb_api_find (id), or a route the catalog lacks (method+path); dry run by default. pick selects fields, max_items caps lists, item_offset skips items. Lists over 60 KB say so.sb_page_openOpen a page for editing and return its outline. Call before any sb_add / sb_set / sb_move / sb_remove. Find page ids with sb_api_find "list pages". Or form_id: edit that form's field document (fields, specials.formRules on its root).sb_page_repairRename a page root that is not "ROOT" (sppro_1, rt_<hex> — left by older seeds) to ROOT, for one page or, without page_id, every page on the site. Draft only; a published page is listed for re-publishing. dry_run (default true) lists what would change.sb_outlineThe open page as a compressed tree — id, type, name, child count, band, and whether a node is a shared global or a site overlay. Never the raw document: a real page is hundreds of KB of JSON.sb_node_readOne node in full — style, config, specials, per-breakpoint overrides, bindings.sb_catalog_searchFind an element type by what it does — or OMIT query to browse every type, the only way to meet one you would not have searched for. detail:true adds the AI hints, as does sb_traits_for. query "icon:<word>" lists icon names.sb_traits_forThis element's INSPECTOR, as a person sees it: tabs, groups, and every control name — with what each DECLARED control writes, and the AI hints for using the element. Read this before styling an element; pass control to read one control in full.sb_addAdd an element — or a whole NESTED subtree — under a parent. One call builds a complete section: pass children rather than calling this once per node.sb_setWrite style, config or specials keys on one node, or on many through edits (one save, one live frame). Per BREAKPOINT by default; base:true writes the fallback layer, right for a value that should not vary.- +25 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Glongus MCP
{
"mcpServers": {
"glongus-mcp": {
"command": "npx",
"args": [
"-y",
"glongus-mcp"
],
"env": {
"GLONGUS_API_KEY": "YOUR_GLONGUS_API_KEY_HERE"
}
}
}
}
Store Builder
{
"mcpServers": {
"store-builder": {
"command": "npx",
"args": [
"-y",
"sbuilder-mcp"
],
"env": {
"SB_API": "YOUR_SB_API_HERE",
"SB_TOKEN": "YOUR_SB_TOKEN_HERE",
"SB_SITE": "YOUR_SB_SITE_HERE",
"SB_SITE_NAME": "YOUR_SB_SITE_NAME_HERE",
"SB_EMAIL": "YOUR_SB_EMAIL_HERE",
"SB_PASSWORD": "YOUR_SB_PASSWORD_HERE",
"PEXELS_API_KEYS": "YOUR_PEXELS_API_KEYS_HERE"
}
}
}
}
Frequently asked questions
Glongus MCP is categorized under E-Commerce and uses a local stdio subprocess. Store Builder belongs to E-Commerce and uses a local stdio subprocess. Pick Glongus MCP for e-commerce work and Store Builder for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Glongus MCP has no declared pricing — check the project's own site. Auth: api key required. Store Builder has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add glongus-mcp and store-builder as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Glongus MCP has a quality signal of 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Store Builder has 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars.
