eCommerce
ambiant.jp
Integrates with Shopify to enable searching products, managing shopping carts, and retrieving store policies.
ENDPOINT 1
https://ambiant.jp/api/mcp
MCP server metadata
- Name
- storefront-renderer
- Version
- 0.1.0
Known tools 5
get_cartGet the cart including items, shipping options, discount info, and checkout url for a given cart id
Inferred read-onlyupdate_cartPerform updates to a cart, including adding/removing/updating line items, buyer information, shipping details, discount codes, gift cards and notes in one consolidated call.
Inferred read-onlysearch_shop_policies_and_faqsUsed to get facts about the stores policies, products, or services.
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.storefront-renderer]
url = "https://ambiant.jp/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"storefront-renderer": {
"type": "http",
"url": "https://ambiant.jp/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: storefront-renderer
Remote MCP URL: https://ambiant.jp/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": {
"storefront-renderer": {
"url": "https://ambiant.jp/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"storefront-renderer": {
"type": "http",
"url": "https://ambiant.jp/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "storefront-renderer",
"transport": "streamable-http",
"url": "https://ambiant.jp/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for ambiant.jp was fetched 2026-08-01T06:57:50.114Z and is being refreshed.
ambiant.jp is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.