In-depth architectural comparison of the Stienhardt Diamond MCP and Store Builder MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Stienhardt Diamond MCP
E-Commerce · Local stdio
Quality: 77/100 (Great) | Auth: No auth required
Store Builder
E-Commerce · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Stienhardt Diamond MCP if you need specialized E-Commerce tools running via a local process. Choose Store Builder if your workspace requires E-Commerce integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Stienhardt Diamond MCP when:
You need dedicated capabilities in the E-Commerce domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Official no-auth MCP server from Stienhardt & Stones with ten tools for sourced diamond education, grading-report verification guidance, face-up size estimates, dated Lab Grown Diamond market context, a 90-entry gemology encyclopedia, and live Stienhardt inventory search. It never verifies a stone itself and directs users to the issuing lab. The hosted Streamable HTTP endpoint is free, stateless, and requires no API key.
Design, fill with real store data, render and publish Store Builder pages from an AI agent.
Tools & Capabilities Breakdown
Stienhardt Diamond MCP Tools (6)
Sourced and dated diamond education
90-entry gemology encyclopedia
Approximate face-up size calculations
Grading-report verification guidance
Diamond specification comparison
Hosted read-only inventory search
Store Builder Tools (37)
sb_connect
Log in, list the sites this account can operate, report which credentials are present
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Stienhardt Diamond MCP is categorized under E-Commerce and uses a local stdio subprocess. In contrast, Store Builder belongs to E-Commerce using local stdio subprocess. Select Stienhardt Diamond MCP when you need capabilities focused on e-commerce and Store Builder when you require tools for e-commerce.
Find API operations by intent — one line per match — then read one operation's call sheet by id: real parameter schemas, the credential it needs, and the body's fields read off the handler that decodes them, each carrying the trap its own doc comment records
sb_api_call
Execute an operation, or any route by method+path; dry run by default. Field selection and local result pagination; `merge` for whole-record PUTs, `If-Match`, multipart `file
sb_page_open
Open a page for editing and return its outline — or, with `form_id`, a form's field document (fields, defaults, dependent-field rules)
sb_outline
The open page as a compressed tree — never a raw document dump
sb_node_read
One node in full, with a warning if it is a shared global
sb_catalog_search
Find an element by what it should do, using the platform's own AI hints
sb_traits_for
An element's inspector — tabs, groups, controls and what each declared one writes — plus its AI hints, defaults and containment rules
sb_add
Add an element — or a whole nested subtree — in one call
sb_set
Write style/config/specials. Per breakpoint by default