vinted-mcp

What this does

vinted-mcp exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

VINTED_AUTH_MODE
VINTED_AUTH_COOKIES
VINTED_AUTH_CSRF_TOKEN
VINTED_AUTH_ACCESS_TOKEN
VINTED_PROXY_URL
VINTED_MAX_CONCURRENCY
VINTED_REQUEST_DELAY_MS
VINTED_MAX_RETRIES

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install vinted-mcp?

Run the Claude Code command in the install section to add vinted-mcp to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with vinted-mcp?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to vinted-mcp as well.

Does vinted-mcp need an API key?

Yes. Before it can run, set these environment variables: VINTED_AUTH_MODE, VINTED_AUTH_COOKIES, VINTED_AUTH_CSRF_TOKEN, VINTED_AUTH_ACCESS_TOKEN, VINTED_PROXY_URL, VINTED_MAX_CONCURRENCY, VINTED_REQUEST_DELAY_MS, VINTED_MAX_RETRIES. They go in the env block of your MCP config.