How to Connect the Vereel MCP Server to Claude, Cursor and Other AI Agents

What you get

MCP, the Model Context Protocol, lets an AI assistant use tools that live outside the chat. The Vereel MCP server is such a set of tools: a small open-source program (Apache-2.0) that runs on your computer, starts when your assistant starts and talks to Vereel's public API with your token. It has 8 tools:

• vereel_list_categories: lists the categories offers are filed under
• vereel_search_offers: searches public offers by words, category, type, platform and language
• vereel_get_offer: shows one public offer with what its page shows
• vereel_list_my_offers: lists your offers and where each one stands
• vereel_get_my_offer: shows one of your offers in full, with what is still missing and the reviewer's note
• vereel_create_offer: creates an offer, which then waits for review
• vereel_update_offer: changes an offer while it is in review
• vereel_add_offer_image: adds a photo from a link or from a file on your computer

What you need

Three things, and no coding:

• Node.js 20 or newer. The assistant starts the server with npx, which comes with Node.js. Check with node --version.
• For anything beyond searching: a Vereel brand account and a read-and-write token from Settings › API tokens. It is shown once, so copy it straight away.
• An app that can run MCP servers. Claude Desktop, Claude Code and Cursor are covered below.

Claude Desktop

Open Claude Desktop's Settings, choose Developer and then Edit Config. That opens a file called claude_desktop_config.json. Add this block, replacing YOUR_TOKEN with your token. If the file already has an mcpServers section, add the vereel entry inside it. Save the file and restart Claude Desktop.

On Windows, if Claude cannot start npx, set "command" to "cmd" and "args" to ["/c", "npx", "-y", "github:hans100x-dotcom/vereel-mcp"].

{
  "mcpServers": {
    "vereel": {
      "command": "npx",
      "args": [
        "-y",
        "github:hans100x-dotcom/vereel-mcp"
      ],
      "env": {
        "VEREEL_API_TOKEN": "YOUR_TOKEN"
      }
    }
  }
}

Claude Code

In Claude Code one command adds the server. Run it in a terminal, replacing YOUR_TOKEN:

claude mcp add vereel --env VEREEL_API_TOKEN=YOUR_TOKEN -- npx -y github:hans100x-dotcom/vereel-mcp

Cursor and other apps

Cursor takes the same block as Claude Desktop, in a file called .cursor/mcp.json in your project or in its MCP settings. Any other app that can start an MCP server from a command needs the same three things: the command npx, the arguments -y github:hans100x-dotcom/vereel-mcp and the VEREEL_API_TOKEN environment variable.

Settings worth knowing

The server reads its settings from environment variables, which in the block above sit under env.

• VEREEL_API_TOKEN: your token. Leave it out and the server only searches public offers.
• VEREEL_READ_ONLY=1: hides the tools that create or change offers. Use it when you only want the assistant to look.
• VEREEL_IMAGE_DIRS: the folders the assistant may upload photos from, for example the folder with your campaign photos. Set it: otherwise the assistant can be asked to upload any image on your computer. Separate several folders with ; on Windows and with : elsewhere.

Check that it works

Restart the app, then ask: “Show me the Vereel categories.” If a list of categories comes back, the server is connected. If you added a token, try: “Which of my Vereel offers are waiting for review?”

If something is wrong, the assistant says what and what to do. The usual cases:

• The Vereel public API is switched off: Vereel can switch its API off at any time. Nothing can be read or changed until it is back, so try again later.
• The token is missing, expired or revoked: create a new one in Settings › API tokens and put it in the configuration.
• The token can only read: create a read-and-write token.
• No Vereel tools in the app: check that node --version shows 20 or higher, that the configuration is valid JSON, and restart the app.

Keep the token safe

The token sits in a configuration file on your computer, which is the right place for it. Keep it out of chats, repositories and screenshots, give it only the access you need, and revoke it in Settings › API tokens if it ever leaks. The article on keeping your Vereel API token safe goes through it.