eCommerce
bettinka.com
An e-commerce MCP server that lets AI assistants search products, retrieve product details, list collections, check inventory, and get store information.
ENDPOINT 1
https://www.bettinka.com/api/mcp
MCP server metadata
- Name
- adcommerce-storefront
- Version
- 1.0.0
This MCP server exposes a single e-commerce store's catalog. Use search_products and get_product to help shoppers find items, list_collections to browse by category, check_inventory for stock, and get_store_info to introduce the store. Product URLs are the store's own pages — send shoppers there to buy.
Known tools 5
get_productFetch full details for a single product by id or handle, including all variants and current stock.
Inferred read-onlyget_store_infoGet high-level information about this store: name, description, currency, supported payment methods, contact, and storefront URL.
Potential side effectsCONNECT 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.adcommerce-storefront]
url = "https://www.bettinka.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"adcommerce-storefront": {
"type": "http",
"url": "https://www.bettinka.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: adcommerce-storefront
Remote MCP URL: https://www.bettinka.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": {
"adcommerce-storefront": {
"url": "https://www.bettinka.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"adcommerce-storefront": {
"type": "http",
"url": "https://www.bettinka.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "adcommerce-storefront",
"transport": "streamable-http",
"url": "https://www.bettinka.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.