eCommerce
lusterandcompany.com
Provides information about Luster & Co. jewellery store, including search, store details, FAQs, service areas, and policies.
ENDPOINT 1
https://lusterandcompany.com/api/mcp
MCP server metadata
- Name
- luster-and-co
- Version
- 1.0.0
Read-only tools for Luster & Co., a custom engagement ring and fine jewellery studio in Vancouver, BC. Use search_jewellery for the catalogue, get_store_info for location and hours, get_faq for policies, and list_service_areas for the cities served.
Known tools 5
get_faqAnswer common questions about diamond certification, lab-grown diamonds, warranty, returns, resizing, appointments and studio location.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.luster-and-co]
url = "https://lusterandcompany.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"luster-and-co": {
"type": "http",
"url": "https://lusterandcompany.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: luster-and-co
Remote MCP URL: https://lusterandcompany.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"luster-and-co": {
"url": "https://lusterandcompany.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"luster-and-co": {
"type": "http",
"url": "https://lusterandcompany.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "luster-and-co",
"transport": "streamable-http",
"url": "https://lusterandcompany.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.