mcp.shop is an MCP server that provides an e-commerce platform implementation using WorkOS AuthKit and Next.js. It connects an MCP-compatible assistant directly to a functioning web shop backend powered by the Next.js B2B Starter Kit, the Vercel MCP Adapter, and Upstash Redis. Designed for developers experimenting with agentic commerce, this server allows AI chat clients to interact securely with a retail backend using established authentication protocols. Users connect to the server and authenticate via AuthKit to trigger commerce actions through standard Model Context Protocol tools. Within an active session, users can place merchandise orders like t-shirts via tool calls, while privileged administrative users can view store order details. By utilizing WorkOS AuthKit with dynamic client registration, mcp.shop demonstrates how identity verification and user permissions operate inside tool-calling workflows, ensuring AI agents act safely on behalf of authenticated accounts rather than relying on unverified commands.
Category: CRM, ERP & E-commerce
Tags: authkit, ecommerce, nextjs, web-shop, workos
bash pnpm install 2. Copy .env.example to .env.local and configure your WorkOS credentials, redirect URI, and Redis configuration. Ensure Dynamic Client Registration is enabled in your WorkOS dashboard. 3. Start the development server: bash pnpm dev 4. Add the server to your MCP client configuration (such as .cursor/mcp.json): json { "mcpServers": { "mcp.shop": { "command": "npx", "args": ["-y", "mcp-remote", "http://localhost:3000/mcp"] } } }Part of MCP Servers
mcp.shop is a sample web store implementation that combines Next.js, WorkOS AuthKit, and the Model Context Protocol. It allows AI clients to authenticate users and execute commerce operations through standard MCP tools.
The server enables users to connect via an MCP client, authenticate using AuthKit, and place merchandise orders through tool calls. Additionally, users with administrative privileges can view store order details directly within their chat environment.
Running the server requires Node.js, a WorkOS account with AuthKit and Dynamic Client Registration configured, and access to a Redis service such as Upstash to manage backend session and application state.
Any MCP-compatible client that supports remote MCP server connections via stdio bridges can connect to mcp.shop, including Cursor and other developer chat clients using the mcp-remote proxy command.
Yes, mcp.shop is open source software released under the MIT license. You can inspect the source code, review its architecture, and contribute via its public GitHub repository.