Omnisend MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OMNISEND_API_KEY | Yes | Your Omnisend API key | |
| OMNISEND_API_URL | No | The Omnisend API URL | https://api.omnisend.com/v5 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Contact schema | Represents a contact in Omnisend. Each contact can be identified by multiple identifiers (email, phone) with corresponding channels. |
| Product schema | Represents a product in the Omnisend catalog. |
| Product category schema | Represents a product category in Omnisend. |
| Event schema | Represents a customer event in Omnisend. |
| Brand schema | Represents brand information in Omnisend. |
| Brand information | Current brand information from Omnisend API. |
TDQS
Scored across 17 tools
Each tool has a clearly distinct purpose targeting specific resources and actions (e.g., createCategory vs. updateCategory, getContact vs. sendEvent). There is no overlap or ambiguity between tools, making it easy for an agent to select the correct one.
Tool names follow a consistent verb_noun pattern throughout (e.g., createCategory, listContacts, updateProduct). All tools use camelCase consistently, with no deviations or mixed conventions, ensuring predictability and readability.
With 17 tools, the server is well-scoped for managing Omnisend's e-commerce and marketing automation domain. Each tool earns its place by covering essential CRUD operations for categories, products, and contacts, along with utility functions like ping and sendEvent.
The tool set provides complete CRUD/lifecycle coverage for categories, products, and contacts, including list, get, create, update, and delete operations. Additional tools like sendEvent and getCurrentBrand fill out the domain, leaving no obvious gaps for agent workflows.