omnisend-mcp.yml
Omnisend ships two first-party hosted, remote MCP servers — the original at https://mcp.omnisend.com/mcp (4 tools) and a v2 at https://mcp.omnisend.com/v2/mcp (7 tools). Both are HTTPS endpoints an MCP client POSTs to directly; there is no npx/stdio package to install. Both are OAuth-protected: an anonymous tools/list returns 401 with a RFC 9728 resource_metadata challenge. Omnisend is additionally listed in Claude's built-in Connector Directory.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Documentation
Documentation link · transport
Tools
omnisend_search— Lists all available Omnisend API operations with short descriptions. Optional `action` filter — query, create, update, delete.omnisend_tool_schema— Retrieves the full JSON Schema (input parameters, required fields, enums) plus curated markdown for a specific API operation.omnisend_reference— Retrieves embedded Omnisend reference documentation by topic — payload examples, event property paths, behavioral hints. Call without topic_id to list topics.omnisend_query— Runs read operations (action=query) — GET requests plus read-shaped analytics POSTs such as reports and statistics.omnisend_create— Creates new resources (action=create) — campaigns, contacts, segments, products, images, email templates, batches.omnisend_update— Updates existing resources or performs state transitions (action=update) — PATCH, PUT, and verb-style POSTs such as send, cancel, tag.omnisend_delete— Deletes resources (action=delete).search— v1 equivalent of omnisend_search.tool_schema— v1 equivalent of omnisend_tool_schema.tool_documentation— v1 equivalent of omnisend_reference.execute— v1 single execution tool — performs any operation regardless of action class. v2 replaced it with four action-scoped tools so clients can route reads away from write paths.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.