vtex.com
VTEX exposes tenant-scoped Commerce HTTP APIs authenticated with either an `appKey`+`appToken` pair or a `VtexIdclientAutCookie` user token, plus the VTEX IO CLI authenticated via `vtex login {accountName}`, and a public unauthenticated VTEX Developer MCP server distributed as an npm/stdin tool.
- VTEX Developer MCPdiscovered
- VTEX Commerce APIsdiscovered
- VTEX IO CLIdiscovered
In the VTEX Admin, create an application key as described in Generating and managing application keys. This gives you an appKey and its paired appToken. Grant the key the needed License Manager roles/resources as described in Managing app key permissions.
Log in to a VTEX store as a shopper or admin. VTEX ID issues a JWT and sets it as the VtexIdclientAutCookie cookie, which can then be sent as the VtexIdclientAutCookie header as documented in API authentication using user tokens.
Install the CLI, then run vtex login {accountName} as shown in Using VTEX IO CLI. The command opens a browser tab where you sign in with your VTEX account email; when the browser shows “You may now close this window.” the CLI session is ready.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing