Commerce Context Layer
Give shopping or marketplace agents semantic and visual product search over a vviinn-powered commerce site.
Overview
com.vviinn/commerce-context-layer is a Build-phase MCP server that connects coding agents to vviinn semantic and visual commerce search and discovery over streamable HTTP.
What is this MCP server?
- Remote streamable-http MCP at api.vviinn.com/mcp with Bearer JWT (read-only) or Basic site credentials
- Semantic and visual search and discovery tuned for agentic commerce workflows
- Context layer version 1.30.0 exposing catalog-aware tools for coding agents
- Credentials issued from vviinn site settings; Authorization header required on every call
- Pairs with agent, API, and ecommerce builds that need live product context in the IDE
- Server version 1.30.0
- Remote endpoint https://api.vviinn.com/mcp (streamable-http)
- Authorization header required (Bearer JWT read-only or Basic site credentials)
What problem does it solve?
Agents cannot see your live catalog, images, or intent-aware product matches unless you bolt on a dedicated commerce context API.
Who is it for?
Indie builders on vviinn who want Claude or Cursor to reason over real product catalogs while coding integrations or agent flows.
Skip if: Teams without a vviinn site, builders who only need generic web scraping, or products with no ecommerce surface.
What do I get? / Deliverables
After you register the remote MCP with site credentials, your agent can run discovery and search against real vviinn commerce data during implementation.
- Registered remote MCP pointing at api.vviinn.com/mcp
- Agent sessions that can invoke commerce context search and discovery tools
- Documented auth pattern for team machines and CI if applicable
Recommended MCP Servers
Journey fit
Agentic storefronts are wired during product build when you connect catalog, search, and checkout context to your coding agent. This remote MCP is an integration surface (streamable HTTP + site-issued auth), not a standalone app feature.
How it compares
Hosted commerce-context MCP integration, not a local SKILL.md workflow or generic database connector.
Common Questions / FAQ
Who is com.vviinn/commerce-context-layer for?
Solo and small-team builders shipping agentic or API-driven commerce on vviinn who want semantic and visual search inside their coding agent.
When should I use com.vviinn/commerce-context-layer?
Use it during Build when you are wiring catalog search, discovery, or merchandising helpers into Claude Code, Cursor, or similar agents against a live vviinn site.
How do I add com.vviinn/commerce-context-layer to my agent?
Add the remote MCP URL https://api.vviinn.com/mcp (streamable-http) and set Authorization to Bearer your read-only JWT or Basic site credentials from vviinn site settings.