How do I get my VTEX API credentials?

Log in to your VTEX Admin, go to **Account Settings → Application Keys**, and create a new App Key. You'll receive an App Key and App Token pair. You also need your Account Name (the subdomain you use to access the VTEX Admin, e.g., 'mystore'). Ensure the key has **Catalog** and **Logistics** read/write permissions. No code, no SDK — just connect and go.

Can my agent update stock levels without opening the VTEX Admin?

Yes! Use the 'manage_stock' tool with a SKU ID and the new quantity. Your agent updates the inventory balance in real-time through the VTEX Logistics API — perfect for warehouse teams receiving shipments who need to update stock counts without navigating to the Inventory module.

How does product search work with categories and brands?

The 'search_products' tool supports three search modes: full-text (e.g., 'Nike Running Shoes'), by brand ID (e.g., 'b/1234'), or by category ID (e.g., 'c/5678'). This means your agent can quickly audit all products under a specific brand or explore an entire product category — no manual catalog browsing required.

Can I create new products and manage my entire catalog via AI?

Absolutely. The 'save_product' tool lets your agent create or update products by sending a structured JSON body. Combined with 'get_category' and 'get_brand' for classification, your agent can handle the full product lifecycle — from initial creation to SKU-level stock adjustments — ideal for merchandising teams managing large VTEX catalogs with thousands of products.

VTEX Catalog MCP Server for AutoGen 7 tools — connect in under 2 minutes

Name: VTEX Catalog
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 7 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add VTEX Catalog as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="vtex_catalog_agent",
            tools=tools,
            system_message=(
                "You help users with VTEX Catalog. "
                "7 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About VTEX Catalog MCP Server

Connect your VTEX Catalog API to any AI agent and manage your entire product catalog through natural conversation.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use VTEX Catalog tools. Connect 7 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

What you can do

Product Search — Run full-text searches across your product catalog by name, brand ID, or category ID. Returns complete product listings with pricing, availability, and images.
Product Details — Retrieve the full specification sheet of any product by ID, including all associated SKUs, categories, dimensions, and metadata.
Product Management — Create or update products directly from your agent. Send structured product data and have it reflected in your VTEX catalog immediately.
SKU Inspection — Look up specific SKUs with detailed attributes like price, weight, dimensions, EAN, and stock status.
Stock Management — Update the available quantity of any SKU across your logistics warehouses. Adjust inventory in real-time without opening the VTEX Admin.
Category & Brand Lookup — Explore your category tree and brand directory to understand how your catalog is organized and ensure correct product classification.

The VTEX Catalog MCP Server exposes 7 tools through the Vinkius. Connect it to AutoGen in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect VTEX Catalog to AutoGen via MCP

Follow these steps to integrate the VTEX Catalog MCP Server with AutoGen.

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 7 tools from VTEX Catalog automatically

Why Use AutoGen with the VTEX Catalog MCP Server

AutoGen provides unique advantages when paired with VTEX Catalog through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use VTEX Catalog tools to solve complex tasks

Role-based architecture lets you assign VTEX Catalog tool access to specific agents. a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive VTEX Catalog tool calls

Code execution sandbox: AutoGen agents can write and run code that processes VTEX Catalog tool responses in an isolated environment

VTEX Catalog + AutoGen Use Cases

Practical scenarios where AutoGen combined with the VTEX Catalog MCP Server delivers measurable value.

Collaborative analysis: one agent queries VTEX Catalog while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from VTEX Catalog, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using VTEX Catalog data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process VTEX Catalog responses in a sandboxed execution environment

VTEX Catalog MCP Tools for AutoGen (7)

These 7 tools become available when you connect VTEX Catalog to AutoGen via MCP:

get_brand

Get details of a brand

get_category

Get details of a category

get_product

Get full details of a specific product

get_sku

Get details of a specific SKU

manage_stock

Update the available quantity of a SKU

save_product

Create or update a product

search_products

Examples: "Coca Cola", "b/1234" (brand ID), "c/5678" (category ID). Search for products by text, brand, or category

Example Prompts for VTEX Catalog in AutoGen

Ready-to-use prompts you can give your AutoGen agent to start working with VTEX Catalog immediately.

"Search for 'Nike Air Max' in my VTEX catalog"

"Update the stock of SKU 12345 to 150 units"

"Show me the details of category 5678"

Troubleshooting VTEX Catalog MCP Server with AutoGen

Common issues when connecting VTEX Catalog to AutoGen through the Vinkius, and how to resolve them.

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

VTEX Catalog + AutoGen FAQ

Common questions about integrating VTEX Catalog MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call VTEX Catalog tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.