Ask ChatGPT, Claude, Gemini or Copilot to plan a program, write and target a message, make artwork or explain a missed send. It works in your real account, with your brand and HRIS data. Nothing sends until your team publishes it.
The ChangeEngine MCP is a Model Context Protocol server that lets an AI assistant work inside your ChangeEngine account. Its 65 tools read programs and past sends, write and schedule messages across email, Slack/Teams, SMS and WhatsApp, target audiences from HRIS data, make on-brand artwork, run surveys and read results.
MCP is the open standard AI assistants use to work with other software. Connect once, sign in as yourself, and your assistant gets the access you have.
See the live tool list →Connect once to the assistant your company approved. Everyone keeps their own permissions.
Plan, draft, target and schedule without five screens.
It reads your programs, segments, voice and send calendar first.
The assistant builds and checks. Your team publishes.
What the assistant calls for six common requests.
Calls: list_subject_dates → list_segments → create_draft → set_message → set_audience → set_schedule → read_timeline
Calls: search_communications → create_follow_up_draft → convert_message → set_schedule → send_me_test
Calls: create_survey → edit_survey → launch_survey → set_message → read_survey_responses
Calls: find_design_template → preview_design_template → create_design → save_design
Calls: read_delivery_forensics → list_send_recipients → read_person_send → list_sync_conflicts
Calls: list_changes_by_program → list_communication_analytics → read_poll_results
Grouped by job. Names match what your assistant shows when it calls them.
The assistant orients itself in your account before it writes anything, and sees what the team is already working on.
Every program in the account, with its ID, so the assistant files new work in the right place.
Ask: "What programs do we have?"
Everything in one program, last edited first, with each message's status and channel. Archived ones are left out.
Ask: "What's in Onboarding?"
Programs ranked by how much work went into them over a window of up to a year. A program with zero changes is a neglected one.
Ask: "What has nobody touched in 60 days?"
The communications and surveys changed most recently, newest first. The fastest answer to what the team is working on.
Ask: "What is the team working on?"
What sends in the next 31 days, by day, with how many people each send reaches. Use it to pick a quiet day before scheduling.
Ask: "Which days next week are crowded?"
Find past messages by meaning rather than exact words, best match first, so nothing gets written twice.
Ask: "Find our last benefits announcement."
The content, audience, schedule, status and review stage of any message, in the same shape the write tools take.
Ask: "Read me the day-one welcome."
The order a person meets each message, grouped by the HRIS date it hangs off. This is how you see the shape of a journey.
Ask: "What does a new hire get in 90 days?"
Who changed a message and when, newest first.
Ask: "Who last edited the holiday message?"
The full approval trail for one message: each step, who took it and any note. A change request explains why it isn't live.
Ask: "Why isn't the reorg message approved?"
A few calls take a message from empty to written, targeted, scheduled and attributed, as a message or a designed newsletter.
A new program, only when no existing one fits.
Ask: "Create a Benefits 2027 program."
An empty email, Slack/Teams or SMS draft in a program, ready for the message, audience and schedule.
Ask: "Start an open enrollment launch draft."
Reach only the people who didn't open, click or answer a survey, or only those who clicked. A segment can't express this, so it's the only way to chase.
Ask: "Chase everyone who didn't click the link."
Change a message's title, description or program.
Ask: "Move the town hall recap to Leadership."
Body, subject, channel and sender in one call, in Markdown or the editor's own format. Supports buttons, images, video, polls, branded email designs and blocks only one segment sees.
Ask: "Write a 120-word welcome for store associates."
Move a message between work email, personal email, Slack and SMS the way the app's editor would. Anything the new channel can't hold is listed.
Ask: "Turn this email into a Slack post."
A designed newsletter built from a short brief with your sections, tone and imagery, and revised by another brief.
Ask: "Build October's company newsletter."
A saved segment, an ad hoc expression built from your HRIS fields, the managers or managers' managers of a group, or a Slack/Teams channel.
Ask: "Send this to Operations managers."
On publish, a fixed date, any HRIS date with day and month offsets, a repeating cadence, after a previous send, or as each person completes a survey. Local time zones supported.
Ask: "Send 7 days before each work anniversary."
Send from the People Team or a named person instead of the default.
Ask: "Send this from the People Team."
Remove a draft that is no longer needed.
Ask: "Archive today's test drafts."
Everything the assistant reads before it writes a word: your brand, your audiences and how many people each channel can actually reach.
Brand voice and tones with their greetings and sign-offs, logos, colors, fonts, AI image style and named email designs.
Ask: "What does our brand voice say?"
Every saved audience, and which can be a base segment.
Ask: "What audiences do we have?"
The conditions behind saved segments, to copy or combine.
Ask: "How is the Field Ops segment built?"
Headcount for a saved segment, split into who is reachable, missing a destination or opted out on a channel, before anything is published.
Ask: "How many Texas hourly staff have a phone number?"
The employee fields and values that can narrow a group, with coverage for each. Special category fields like gender or religion show coverage, never values.
Ask: "Which fields find night-shift staff?"
Every personalization field this message can use, including manager fields and calendar events. Valid tags depend on the audience.
Ask: "What can I personalize here?"
The HRIS dates this account can schedule from, such as start date, birthday, anniversary or became a manager.
Ask: "What dates can trigger a message?"
Postable Slack channels, by name or most used.
Ask: "Which channels do we post to most?"
Use the approved artwork you already own, make more from your branded designs, check how copy fits, and file the result back in the library.
Host a PNG, JPEG, WebP or AVIF up to 100 MB at a durable URL, and optionally file it in the library with tags.
Ask: "File this photo under Recognition."
A one-time upload URL for a full-quality image or PDF.
Ask: "Upload the benefits guide PDF."
Uploaded files and branded designs in the content library, by folder, so messages use approved artwork first.
Ask: "What onboarding artwork do we have?"
Tag names and folder paths, with counts.
Ask: "How is our library organized?"
Drop an editable branded design into a message.
Ask: "Put the holiday banner in this email."
Branded layouts in 13 formats: posters, certificates, social posts, banners, TV displays, guides, FAQs, video call backgrounds, manager one-pagers and more.
Ask: "Find a certificate design."
Render a layout with your content before creating it.
Ask: "Preview the poster with this headline."
An editable design with your copy and images in place. It stays a real design, not a flat picture.
Ask: "Make an open enrollment poster."
Every element, its text, size and position.
Ask: "What text is on the banner?"
See changes before saving, with warnings when copy would shrink past legibility or push an element off the canvas.
Ask: "Show it with the date changed."
Change copy, color, images and position, and keep it.
Ask: "Swap the photo and use our blue."
File a finished design in the content library.
Ask: "Save the poster for the team."
Turn a PDF into an editable design in the library.
Ask: "Make our one-pager editable."
Unsplash photos for a design, credited to the photographer.
Ask: "Find a warehouse team photo."
The Meta-approved WhatsApp messages this account can send.
Ask: "What WhatsApp messages can we send?"
Who a message can come from, and who it uses now.
Ask: "Who can this come from?"
The assistant checks its work the way a recipient will see it.
The subject, sender and body of one message.
Ask: "Read back what you wrote."
The message rendered as recipients will see it, with sample merge values, returned as an image.
Ask: "Show me how it looks in an inbox."
A real test copy to your email, Slack, Teams, SMS or WhatsApp.
Ask: "Send me a test on Slack."
The full survey lifecycle, from first draft and translation through launch to reading the answers back by theme.
A draft survey, optionally confidential (personal details hidden, results under 5 answers suppressed, eNPS enabled) or open to anyone by QR code or link.
Ask: "Create a confidential Austin pulse."
Pages, questions and logic in one checked call: single and multiple choice, dropdown, rating, yes or no, text and comment, with conditional display. If one edit fails, none are saved.
Ask: "Show the comment box only below 3 stars."
Every string, ready to translate into a language.
Ask: "Get this ready for Spanish."
Store the translated strings on the survey.
Ask: "Add the Spanish version."
Publish the survey and return its link for a message.
Ask: "Launch it and add the link to day 30."
Stop taking answers, with your own closing note.
Ask: "Close the pulse on Friday."
Take a survey out of the list.
Ask: "Archive last year's survey."
Surveys with status and response counts.
Ask: "Which surveys are live?"
Questions, settings and which version people see.
Ask: "What does our onboarding survey ask?"
Counts per answer, open text grouped by theme, and whole responses. Never tied to a person, and anonymous results stay hidden until 5 answers.
Ask: "Summarize the 90-day survey."
Sends, deliveries and clicks for each message carrying the link.
Ask: "How many people got the survey?"
Delivery, opens, clicks, errors, reactions and poll answers for anything that has sent, down to why one person missed a message.
Messages ranked by opens, clicks, deliveries, errors or sends in a time window, with your account's average per channel to compare against. Slack and Teams opens are reported as unmeasured.
Ask: "What had the lowest opens last quarter?"
Deliveries, bounces, clicks by link, failures by reason and the people who engaged, for each recent send.
Ask: "Who missed Monday's announcement?"
Every recorded recipient of a send, by outcome or channel.
Ask: "List who the safety alert reached."
Why one person did or did not get a message: published, in the audience, reachable, opted out or queued, over the last 90 days.
Ask: "Why didn't Jordan get the benefits email?"
Answers to polls inside a message. Never tied to a person.
Ask: "What did people vote for?"
People the last HRIS sync couldn't place because of a duplicate record. They get nothing until the HRIS is fixed.
Ask: "Is anyone missing because of the HRIS?"
Add ChangeEngine in your assistant and sign in.
Describe the program, message or survey. It reads your account first.
Drafts, audiences and schedules land in ChangeEngine, previewed and test-sent to you.
Review and publish in ChangeEngine. Ask for results any time.
Native to each channel, and able to move a message between email, Slack and SMS without a rewrite.
Write, design as a newsletter, preview and test.
The same, for people without a work inbox.
Post to people or channels, convert from email, read reactions.
Post to people or channels and send tests.
Two-way text, with a check of who has a number first.
Approved WhatsApp messages with merge tags and links.
There is no new app for employees, no code to maintain and nothing to host. ChangeEngine connects to the systems IT already runs through standard, auditable integrations.
SOC 2 and ISO 27001 certified and GDPR compliant, with documentation ready in the Trust Center.
SAML or OAuth single sign-on with optional 2FA. Employees reach the hub with Google or Microsoft sign-in.
Encryption in transit and at rest, with data residency in the US, EU or Canada. Content is generated inside your ChangeEngine environment.
The MCP runs inside the assistant you already approved and acts with the signed-in user's permissions. Nothing sends without an approval.
Workday, ADP, BambooHR, UKG and 75+ more, plus Active Directory, Teams, Slack and SharePoint, all through standard APIs.
Role-based permissions and approval steps, so comms, legal and leadership sign off before anything goes out.
Our MCP roadmap is public, and shipped items keep the votes that asked for them.
See the live list and vote →The Employee Hub AI MCP adds sections, apps and pages to your hub.
See Employee Hub AI →The ChangeEngine MCP is a Model Context Protocol server that lets an AI assistant work inside your ChangeEngine account. Its 65 tools read programs and past sends, write and schedule messages across email, Slack/Teams, SMS and WhatsApp, target audiences from HRIS data, make on-brand artwork, run surveys and read results.
ChatGPT, Claude, Gemini and Microsoft Copilot, plus any assistant that supports MCP connectors. Your assistant connects once, you sign in with your own ChangeEngine account, and it can use every tool your role allows.
No. Employee data and content that the ChangeEngine MCP reads or writes is not used to train AI models.
No. The MCP creates, targets and schedules drafts, previews them as recipients will see them and can send a test copy to you. A person on your team publishes every communication in ChangeEngine, through your normal review and approval flow.
Work email, personal email, Slack, Microsoft Teams, SMS and WhatsApp. It can also build a designed newsletter and move a message between email, Slack and SMS.
Yes. It sends on publish, on a fixed date, relative to any date your account holds (start date, birthday, anniversary, became a manager) with day offsets and day-of-week rules, on a repeating cadence, after an earlier send, or as each person completes a survey, in each recipient's local time.
Yes. A follow-up reaches only the people who didn't interact, didn't answer a survey or didn't click a link, or only those who clicked. It inherits the original audience and waits a delay you choose.
It reads your saved segments, the fields you can filter on and their coverage, live headcounts and channel reach before anything is published. It can target a segment, a custom expression, the managers of a group or a Slack/Teams channel.
Yes. It drafts surveys with 7 question types, conditional logic and confidential mode, translates, launches and closes them, and reads responses back with open text grouped by theme. Anonymous results stay hidden until 5 people answer.
Sends, deliveries, errors, opens, clicks by link, reactions and poll answers for anything that has sent, with your account's channel averages to compare against. It can list every recipient of a send and explain why one named person did or didn't get a message.
No. You sign in as yourself, so the assistant sees and does exactly what your ChangeEngine role allows. Sensitive fields such as gender or religion report coverage only, never values.
It runs on the ChangeEngine platform: ISO 27001 and SOC 2, GDPR compliant, SSO, encryption in transit and at rest, and US, EU or Canada data residency. Every change is recorded in the communication's history.
Yes. Employee Hub AI has its own MCP, so an assistant can add sections, apps and pages to your hub from chat.
Connect once and ship your next program from a single prompt.