
CatalogEngine
CatalogEngine is a MCP server that helps agents structure e-commerce inventory and catalog data over a remote SSE endpoint.
About
CatalogEngine is a remote Model Context Protocol server aimed at developers and small teams who sell physical or digital products and need their AI coding agent to reason over inventory and product catalog structure instead of ad-hoc JSON blobs. You connect it through an SSE remote endpoint in Claude Code, Cursor, Codex, or similar hosts so the agent can help normalize SKUs, attributes, variants, and stock-related fields as you implement backends, admin tools, or sync jobs. It sits in the build phase as backend-oriented tooling: use it while you are defining how products map to your database, APIs, and storefront layers, not as a substitute for market validation or launch SEO. Premium calls may require a Base64 EIP-3009 TransferWithAuthorization signature in the payment-signature header, so budget for that flow if you hit gated capabilities. Pair it with your own commerce stack choices (Stripe, Shopify API, custom Postgres) rather than expecting a full hosted store.
- Remote MCP over SSE at catalog-engine-mcp.vercel.app for agent-driven catalog operations
- Focused on e-commerce inventory and catalog data structuring
- Optional premium settlement via EIP-3009 payment-signature header on remote calls
- Version 1.0.0 CatalogEngine server in official MCP server schema
- MCP integration you register in the client—not a local refactor or audit skill
CatalogEngine by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport sse catalog-engine https://catalog-engine-mcp.vercel.app/api/mcp --header "payment-signature: YOUR_PAYMENT_SIGNATURE"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | SSE |
|---|---|
| Auth | Required |
What it does
Structure product SKUs, variants, and inventory fields so your storefront or agent can read consistent catalog data.
Who is it for?
Best when you're wiring a custom shop, internal catalog API, or agent-assisted PIM on top of your own database.
Skip if: Skip if you only need a hosted storefront with no custom catalog modeling, or anyone avoiding remote MCP and payment-signature flows.
What you get
After you register the remote MCP server, your agent can work against a clearer catalog and inventory model while you implement backend and integration code.
- Agent-accessible catalog and inventory structuring workflows over MCP
- Consistent field and entity conventions for products and stock in your codebase
- Registered remote CatalogEngine connection in your agent environment
By the numbers
- MCP server schema 2025-12-11
- Server version 1.0.0
- Single remote SSE endpoint (catalog-engine-mcp.vercel.app)
Recommended MCP Servers
How it compares
MCP catalog structuring server, not a Shopify theme skill or a one-shot landing-page generator.
FAQ
Who is CatalogEngine for?
Developers building e-commerce or marketplace products who want their coding agent to help organize inventory and catalog fields via MCP.
When should I use CatalogEngine?
Use it during the build phase while you design backend models, APIs, and sync logic for products, variants, and stock—not before you have validated that you are selling something.
How do I add CatalogEngine to my agent?
Register the remote SSE URL https://catalog-engine-mcp.vercel.app/api/mcp in your MCP client config; supply the secret payment-signature header only if premium settlement is required for your tenant.