Omnisend MCP Server

by plutzilla

267 downloads

Not rated

GitHub

Other

About

Omnisend MCP Server is a Model Context Protocol server that integrates with the Omnisend API V5, written in TypeScript. It allows MCP-compatible clients (AI assistants, VS Code, custom apps) to manage Omnisend contacts, products, events, categories, and brand information.

Details

Author: plutzilla
Downloads: 267
Categories: Other

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Omnisend MCP Server

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

From the repository

Install dependencies with npm install, build with npm run build, create a .env file with OMNISEND_API_KEY, then start the server with npm start. The server can be used with Claude Desktop (via configuration in claude_desktop_config.json) or with other MCP clients. For debugging, run npm run inspect to launch the MCP Inspector.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "omnisend mcp server": {
            "omnisend": {
                "command": "node",
                "args": [
                    "/path/to/dist/index.js"
                ],
                "env": {
                    "OMNISEND_API_KEY": ""
                }
            }
        }
    }
}

McpServers

{
    "omnisend": {
        "command": "node",
        "args": [
            "/path/to/dist/index.js"
        ],
        "env": {
            "OMNISEND_API_KEY": ""
        }
    }
}

Omnisend MCP Server

A Model Context Protocol (MCP) server that integrates with Omnisend API V5, written in TypeScript.

Version: 2.3.0

Features

- Contact management (list, create, get, update)
- Product management (list, create, get, replace, delete)
- Event tracking
- Product categories management
- Brand information access
- Cursor-based pagination support with next/previous URLs and limit/offset information
- MCP Inspector integration for debugging and testing
- Human-readable resource names with proper JSON schema responses

Changes in Version 2.3.0

- Added brand information support with /v5/brands/current endpoint integration
- Implemented getCurrentBrand tool for retrieving current brand data
- Added Brand information resource for live brand data access
- Added Brand schema resource with proper JSON schema definition
- Updated all schema resources to return serialized JSON instead of dummy text
- Improved resource naming with human-readable names and "schema" suffix
- Added MCP Inspector integration with npm run inspect and npm run inspect:env scripts
- Enhanced debugging capabilities with visual testing interface
- Updated documentation with comprehensive debugging and testing guide

Changes in Version 2.2.0

- Refactored codebase to a more modular structure
- Implemented domain-specific modules (contacts, products, categories, events)
- Organized code into logical directories (/types, /filters, /api-resources, /resources, /tools)
- Made server version dynamic in the ping tool
- Added better error handling in API requests
- Improved code maintainability with barrel exports
- Removed redundant and duplicate code

Changes in Version 2.1.0

- Updated to @modelcontextprotocol/sdk v1.11.0
- Improved error handling throughout the application
- Enhanced API stability with better error messages
- Added request timeout configuration to prevent hanging connections
- Fixed SSE connection issues with MCP Inspector
- Optimized console output to be compatible with MCP clients
- Added cursor-based pagination context in MCP responses (next/previous URLs, limit/offset)

Changes in Version 2.0.0

- Migrated entire codebase to TypeScript
- Updated MCP resource structure according to latest specification
- Added proper type declarations for all API responses and requests
- Improved error handling with typed exceptions
- Enhanced code organization and maintainability

Installation

npm install

Building

To compile TypeScript code:

npm run build

Running in Development Mode

For development with auto-reloading:

npm run dev

Debugging and Testing

MCP Inspector

The project includes scripts to run the MCP Inspector for testing and debugging:

```bash

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

Claude Desktop / Cursor

McpServers

Omnisend MCP Server

Features

Changes in Version 2.3.0

Changes in Version 2.2.0

Changes in Version 2.1.0

Changes in Version 2.0.0

Installation

Building

Running in Development Mode

Debugging and Testing

MCP Inspector

Install

More like this

Sequential Thinking

Filesystem

EverArt

Google Drive

Reactive Resume

FastMCP v2 🚀