VTEX MCP: ask about your store in 
Claude & 
ChatGPTPorter Metrics connects VTEX to Claude, ChatGPT and other AI clients through one hosted MCP server. MCP is the Model Context Protocol, the open standard AI apps use to reach other tools. Ask what the store really sold yesterday, which SKUs carry the month or where stock ran out, and the answer comes from your live VTEX account.
Every field and its definition is in the VTEX fields list.
One server, every VTEX store: Porter connects VTEX to the AI clients, fields and workflows e-commerce teams already use. The same Porter server URL works in Claude, ChatGPT and any MCP client that supports remote servers. Porter calls VTEX’s APIs with the application key you give it, as VTEX’s guide to API authentication with API keys describes.
Works in: Claude (Claude.ai, Claude Desktop, Cowork and Claude Code), ChatGPT and any MCP client that supports remote servers.
Orders: Orders · Order Value · Units · Items Value · Shipping · Tax · Discounts
Order lines: Line Revenue · Line List Value · Quantity Sold
Catalog: SKUs
Inventory: Stock On Hand · Stock Reserved · Stock Available
Orders: Order Date · Order ID · Order Status · Sales Channel · Sales Channel ID · Payment Methods · Origin · Seller · Currency · Has Return Invoice
Products: Product Name · Product ID · SKU Name · SKU ID · Reference Code · Brand · Category · SKU Active
Inventory: Warehouse · Warehouse ID · Unlimited Stock
Porter has 36 ready-made VTEX fields, 14 metrics and 22 dimensions. Each one is in the full VTEX field reference.
Orders · Order lines · SKU catalog · Inventory per warehouse. Each table answers its own questions. Product Name lives in the catalog, so ask for SKU Name, Brand and Category when you want them next to Line Revenue. Catalog and inventory are today’s, whatever the date range.
Send work from Claude or ChatGPT to: email on a schedule
Turn answers into: live dashboards · client reports · weekly summaries
More servers for the same chat: all MCP connectors
Porter’s VTEX MCP reads orders, the catalog and inventory and leaves your store as it is. Claude reports on what sold and what’s in stock while orders, prices and stock levels stay exactly as you set them in the VTEX admin. You choose the key Porter uses and its role, and can switch it off anytime.
Every VTEX question is a report. Order edits, price changes, promotions and stock updates stay in the VTEX admin, where you handle them as usual.
Generate an application key just for Porter, with a role that reads orders, the catalog and inventory. VTEX’s guide to application keys explains that new keys start with no permissions and get access only through the roles you add.
Porter leaves out the customer name, email, document and shipping address that come with each order. Customer records in VTEX Master Data aren’t part of the connector.
Deactivate Porter’s key in the VTEX admin and the connection stops at once, without touching your other integrations. Generate a new key pair to reconnect.
Porter’s VTEX MCP uses one server URL in every AI client, plus your VTEX account name and an App Key with its App Token. Claude takes Porter as a plugin or a custom connector. ChatGPT takes it through the Porter Metrics app or developer mode. Both read the same stores, with the same 36 fields.
yourstore.myvtex.com. Porter also accepts the admin URL and keeps the name.Use the Claude plugin for the guided setup. Claude keeps the Porter plugin synced when new tools ship.
portermetrics/porter.portermetrics/porter.Anthropic’s guide to custom connectors using remote MCP walks through the same path, and custom connectors work on Free plans with a limit of one. The Claude-specific setup and use cases live on the VTEX connector for Claude page.
Use manual setup when Claude asks for a custom connector instead of a plugin.
Porter.https://mcp.portermetrics.com/mcp.Use the Porter Metrics app for the fastest ChatGPT route.
OpenAI documents connected apps in ChatGPT and custom MCP servers in ChatGPT developer mode.
Use developer mode when you want the full Porter setup in ChatGPT: connector plus skill.
Porter Metrics.https://mcp.portermetrics.com/mcp as the MCP Server URL.https://mcp.portermetrics.com/skill.zip.skill.zip to your ChatGPT project.VTEX’s own server, the VTEX Developer MCP, has no URL to paste: it runs on your machine and reads VTEX’s documentation, not your store. Use Porter’s URL above to ask about your own orders, SKUs and stock, next to your other channels.
Try this one once you’re connected:
Each VTEX skill in Porter’s MCP is a ready-made prompt for one question an e-commerce team asks every week. A skill turns live store data into a net sales report, a best-seller list, a stock-out check or a scheduled email. Copy a prompt into Claude or ChatGPT, then change the dates, channels or thresholds to fit your store.
The research skills blend VTEX with your ad, analytics, email or other store accounts, so connect Meta Ads, Google Ads, GA4, Klaviyo or the Shopify MCP in Porter first.
These run on a schedule and send what they find, while your VTEX store stays as it is.
E-commerce marketers who run a VTEX store and answer for its numbers get the most from Porter’s MCP. Agencies, paid media teams and marketing analysts use it to turn a store question into a net sales report, a best-seller list or a stock-out check, without exporting orders from the admin.
Marketers who sell on VTEX and report on it next to their ads.
Your daily sales number includes orders that were later cancelled. The real question is what got invoiced.
You build VTEX apps or integrations and want help with docs and endpoints. VTEX’s Developer MCP covers that job, and you can run it next to Porter.
VTEX’s own VTEX Developer MCP and Porter’s MCP do different jobs. VTEX’s Developer MCP guide describes a local server that searches VTEX documentation and API references for AI coding tools. Porter is a hosted MCP for marketers: connect your store once, ask about orders and stock, and see VTEX next to your other channels.
VTEX’s MCP helps you build on VTEX. Porter’s MCP hands your AI your store next to everything that brings buyers to it.
Both speak MCP and work in Claude. Here is where they part.
| Porter | VTEX Developer MCP | |
|---|---|---|
| Same job, different reach | ||
| Built for | Marketers, agencies and analysts | Developers building on VTEX |
| Where it runs | Hosted by Porter at mcp.portermetrics.com/mcp | On your own machine, with Node.js 18 or newer |
| What it reads | Your store’s orders, order lines, SKUs and stock | VTEX documentation and API references |
| Tools | 36 ready-made fields in four tables | 4 tools: search docs, fetch a doc, search endpoints, endpoint details |
| Works in | Claude, ChatGPT and any remote MCP client | Cursor, VS Code with GitHub Copilot, Claude Code, Claude Desktop and Gemini CLI |
| Price | Included in every Porter plan, the free plan too | No price listed in VTEX’s guide |
| Only one side | ||
| Meta, Google, GA4 and Klaviyo in the same answer | Yes, from Porter’s 30+ data sources | — |
| Live dashboards at their own link | Yes | — |
| Scheduled reports by email | Yes | — |
| Skills: whole store tasks, already written | Yes | — |
| VTEX docs search and endpoint specs | — | Yes |
VTEX’s column follows VTEX’s Developer MCP guide and VTEX’s release note on the AI Developer Toolkit (as of November 2026).
Use VTEX’s own if you write VTEX code. Everything under Only one side is what happens when the store is one channel among several. Both servers can sit in the same Claude account.
“VTEX MCP” names a few different servers. The job decides which one you want.
A few rank for this search, and they split two ways.
Porter reads your store next to your marketing from one hosted server, starting on the free plan. For other store platforms, see the WooCommerce MCP.
Every Porter plan includes the VTEX MCP at no extra cost, the free-forever plan too. Porter bills Reporting per connected data source account, and each VTEX store counts as one. VTEX questions are reads, so they use no automation credits. Full details are on Porter pricing.
| What you use | What you pay | What is included |
|---|---|---|
| VTEX MCP | Included in every plan | The server URL, Claude and ChatGPT setup, reports, skills and scheduled emails |
| Reporting | From $12.50/mo per data source account, billed annually | Reports and dashboards across VTEX and your other sources. The free plan keeps unlimited connected accounts, up to 30 days of history and 15 days in AI chats |
| Automation | By credits | Approved changes on your other sources, such as pausing a Meta ad. The free plan includes 100 credits a month |
Free means usable: the free plan connects unlimited VTEX stores, keeps up to 30 days of history and gives you 100 credits a month.
Yes. VTEX ships the VTEX Developer MCP, a local server that gives AI coding tools VTEX’s documentation and API references. It doesn’t read your store’s orders or stock. Porter’s VTEX MCP runs at https://mcp.portermetrics.com/mcp, reads your store with your App Key and App Token and puts it next to your other channels.
Porter’s VTEX MCP server URL is https://mcp.portermetrics.com/mcp. Paste it into Claude, ChatGPT or another AI client as a custom connector, then connect your store with its account name, App Key and App Token. VTEX’s Developer MCP has no URL: you start it on your machine with npx.
Porter’s VTEX MCP is included in every Porter plan, the free-forever plan too. The free plan covers unlimited connected accounts, up to 30 days of history, 15 days in AI chats and 100 automation credits a month. Paid Reporting starts at $12.50 a month per data source account, billed annually, and the 14-day trial needs no card.
Yes. Each store connects with its own account name, App Key and App Token and bills as one data source account. Agencies add every client’s store the same way, then name the store they mean when they ask. The free plan connects unlimited stores.
Porter reads orders, order lines, the catalog and inventory. Customer records in VTEX Master Data stay out, and so do the customer name, email and address on each order. For customer lists and segments, use the VTEX admin as usual.
Your store’s. VTEX keeps order dates in UTC, and Porter dates each order in the time zone its sales channel declares, so yesterday in Claude is yesterday in your admin. If a channel declares a zone Porter doesn’t map yet, Claude names it in an error instead of moving orders to the wrong day.
MCP is the Model Context Protocol, an open standard for connecting AI applications to tools like VTEX. MCP isn’t the agent. Claude and ChatGPT are the agents, and Porter’s MCP is how they reach your store.
Ask for invoiced orders first: VTEX counts cancelled orders in sales totals until you filter by Order Status. Order Value includes shipping and tax, while Line Revenue doesn’t. And a day in Porter is the store’s local day, not the UTC day. Those three explain most gaps.
VTEX lists at most 30 pages of orders per request, so Porter splits a long date range into smaller ones and then reads each order. A month of a large store can take a while the first time. Catalog and inventory questions read every SKU, so they take longer than order questions.
Generate a new App Key and App Token in the VTEX admin and reconnect them in Porter. Porter stops after VTEX rejects the key pair twice in a row, for example when the key was deactivated. If VTEX answers 403 instead, the key works but its role can’t read that data, so add the missing role.
Connect VTEX to Claude or ChatGPT and start with invoiced sales reports, best-seller lists and stock-out emails that land in your inbox.
Start free: unlimited connected accounts on the free-forever plan, or a 14-day trial with everything unlimited and no card.