Skip to main content
Glama
plutzilla

Omnisend MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OMNISEND_API_KEYYesYour Omnisend API key
OMNISEND_API_URLNoThe Omnisend API URLhttps://api.omnisend.com/v5

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
pingA

Simple tool to check if the MCP server is running correctly.

listContactsA

Retrieve a list of contacts from Omnisend. Each contact can be identified by multiple identifiers (email, phone) with corresponding channels. The response includes pagination information (next/previous cursor, limit, offset).

createContactB

Create or update a contact in Omnisend. Contact data can include identifiers (email, phone), personal information, subscription status, and custom properties.

getContactB

Retrieve detailed information about a specific contact by their unique identifier.

updateContactA

Update an existing contact's information. IMPORTANT: You must first get the contact using getContact and preserve the returned structure when updating. The update request requires the same structure as returned by the GET method, with only your desired changes applied.

listProductsB

Retrieve a list of products from the Omnisend catalog with pagination support. The response includes pagination information (next/previous cursor, limit, offset).

createProductB

Create a new product in the Omnisend catalog. Product data can include details like title, description, variants, images, price, and more.

getProductB

Retrieve detailed information about a specific product by its unique identifier.

replaceProductA

Replace an existing product with new data. IMPORTANT: You must first get the product using getProduct and preserve the returned structure when replacing. The replace request requires the same structure as returned by the GET method, with only your desired changes applied.

deleteProductB

Remove a product from the Omnisend catalog by its unique identifier.

listCategoriesA

Retrieve a list of product categories from the Omnisend catalog with pagination support. The response includes pagination information (next/previous cursor, limit, offset).

createCategoryB

Create a new product category in the Omnisend catalog. Category data can include title, description, image, and URL.

getCategoryB

Retrieve detailed information about a specific product category by its unique identifier.

updateCategoryA

Update an existing product category. IMPORTANT: You must first get the category using getCategory and preserve the returned structure when updating.

deleteCategoryB

Remove a product category from the Omnisend catalog by its unique identifier.

sendEventB

Send a customer event to Omnisend. Events are used to track customer behavior and can trigger automations. Can be custom events or predefined system events.

getCurrentBrandB

Retrieve information about the current brand from Omnisend. This includes brand ID, website, platform, version, currency, and other brand-related details.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Contact schemaRepresents a contact in Omnisend. Each contact can be identified by multiple identifiers (email, phone) with corresponding channels.
Product schemaRepresents a product in the Omnisend catalog.
Product category schemaRepresents a product category in Omnisend.
Event schemaRepresents a customer event in Omnisend.
Brand schemaRepresents brand information in Omnisend.
Brand informationCurrent brand information from Omnisend API.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/plutzilla/omnisend-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server