Skip to main content

About the MessageGears MCP server

The MessageGears MCP server lets you drive your MessageGears account from an AI assistant (such as Claude) using natural language. Instead of clicking through the UI or writing API calls, you describe what you want, for example "build an audience of customers who purchased in the last 30 days and haven't opened an email since" or "set up a campaign from the spring sale template and run the launch checklist", and the assistant uses a defined set of tools to do it in your account.

MCP (Model Context Protocol) is an open standard for connecting AI assistants to external systems. The MessageGears MCP server is our implementation: a secure bridge between your AI assistant and the MessageGears platform. It builds on the same permissioned layer as the MessageGears automation APIs, exposing those capabilities as tools an AI assistant can call in conversation instead of you writing code against the API.

Version notice

The MessageGears MCP server requires Accelerator version 26.3.2 or later.

Availability

The MessageGears MCP server is available now. MessageGears professional services will help enable it for your account; contact your account team to get started.

For information on our Accelerator "Agent API" endpoints, see our Stoplight documentation.

What you can do with it​

  • Build, inspect, and size audiences, including safe test audiences
  • Create and set up campaigns, run the pre-launch checklist, and check send job status
  • Manage external campaigns that deliver audiences to destinations such as ad platforms
  • Author and manage templates, including SMS and push-notification content
  • Write channel-appropriate copy that respects each channel's real limits

Campaign and send analytics are coming soon; see Coming soon.

The server also bundles skills: short guides the assistant consults on its own so it applies MessageGears' own rules rather than generic ones, covering audience building, personalization, copy limits, launch safety, and more.

For the full capability map, see MCP server capabilities.

Who it's for​

  • Marketers who want to go from brief to a checked, launch-ready campaign in one conversation instead of a dozen screens.
  • Lifecycle and audience owners who iterate targeting by describing it, watching the row count change as the definition is refined.
  • Operations and technical users who want a natural-language front door to campaign setup and status.

No engineering knowledge is required for everyday use.

How a request works​

  1. You describe a goal in natural language.
  2. The assistant picks the right tool or tools, and asks you to clarify if anything is ambiguous.
  3. For anything destructive or irreversible, such as deleting a template, the assistant stops and asks you to confirm before acting.
  4. Results come back as readable summaries: tables for lists, status for send jobs, and links into Accelerator for the objects it creates or changes.

To learn more about confirmation gates and data handling, see MCP server safety and privacy.

What it does not do​

  • It is not a replacement for the MessageGears UI. It is a faster path for common tasks and exploration.
  • Available tools depend on your Accelerator version and plan. If you ask for something your account doesn't support, the assistant tells you rather than failing silently.