Vereel MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VEREEL_API_URL | No | The Vereel API base URL. Default https://www.vereel.com/api/v1/public. http:// is accepted only for localhost. | https://www.vereel.com/api/v1/public |
| VEREEL_API_TOKEN | No | Your brand token (vrl_…), created in Vereel under Settings › API tokens. Without it the server can only search public offers. | |
| VEREEL_READ_ONLY | No | Set to 1 to hide the tools that create or change offers. Use it with a token you only want to read with. | |
| VEREEL_IMAGE_DIRS | No | Folders the assistant may upload photos from, separated by ';' on Windows and ':' elsewhere. Default: any folder. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vereel_list_categoriesA | List the categories Vereel files offers under (for example beauty, fashion, travel). Their ids are what vereel_create_offer takes as categoryIds and vereel_search_offers takes as category. No token needed. |
| vereel_search_offersA | Search the influencer-marketing offers (campaigns) that brands have published on Vereel and that creators can apply to, newest first. Filter by words, category, type, platform and language. Shows what an anonymous visitor of the site sees: no payment amounts. Use nextCursor to get the next page. No token needed. |
| vereel_get_offerA | Get one public Vereel offer with the details its page on vereel.com shows: what the creator does, deliverables, platforms, audience, follower minimum, apply-by date and the link to the offer's page. No payment amounts. No token needed. |
| vereel_list_my_offersA | List the offers the brand that owns the token has created through the API, newest first, with each one's status: in_review (waiting for Vereel), active (public), rejected (with Vereel's note) or closed. Use it to check progress or to find an offer's id. Needs a brand token (read or read-and-write). |
| vereel_get_my_offerA | Get one offer the brand created through the API, in full: every field, its status, the photos, what is still missing before Vereel can approve it, and the reviewer's note if it was rejected. Needs a brand token (read or read-and-write). |
| vereel_create_offerA | Add an offer (an influencer-marketing campaign) to Vereel for the brand that owns the token, so creators on Instagram, TikTok, YouTube or X can find it and apply. The offer is NOT public yet: Vereel reviews every offer sent through the API and publishes it once approved. It needs at least one photo before it can be approved: pass imageUrls, or add one afterwards with vereel_add_offer_image. Get categoryIds from vereel_list_categories. Show the user the campaign details and get their go-ahead before calling, because this sends the offer to Vereel's reviewers. Needs a read-and-write brand token. |
| vereel_update_offerA | Change an offer the brand created through the API, while it is still in review. Only the fields you give change. To reorder or remove photos, pass photos with the offer's current photo URLs in the new order (leaving one out removes it); to add a photo use vereel_add_offer_image. An offer that is already public or rejected cannot be changed through the API. Needs a read-and-write brand token. |
| vereel_add_offer_imageA | Add one photo to an offer that is still in review. Give either imageUrl (an https link Vereel downloads) or filePath (an image on the machine this server runs on, which is uploaded for you). JPEG, PNG or WebP, at most 5 MB, at most 6 photos per offer; the first photo is the cover. Needs a read-and-write brand token. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: category listing, public offer search/get, brand-owned offer list/get, create, update, and image addition. The public-versus-owned offer distinction is explicitly reinforced in the descriptions, so list_my_offers/get_my_offer are unlikely to be confused with search_offers/get_offer.
All tools use the same vereel_ prefix and consistent snake_case verb_noun naming. Variants such as list_my_offers and get_my_offer predictably signal ownership scope.
Eight tools is a well-scoped set for an offer-management API, covering browsing, reading, creating, updating, and adding images. Each tool earns its place without obvious redundancy.
The core offer lifecycle is well covered: categories, public discovery, brand-owned listing/getting, creation, in-review updates, and image upload. Minor gaps remain around deleting or closing an offer and managing applications, but the main brand workflow is supported.