ChangeEngine
ChangeEngine MCP →
EXOS MCP · Internal

Build suites, hubs and invites from Claude

The EXOS MCP drives the same build queue, hub editor and invite flow as changeenginelabs.ai. This page is for the ChangeEngine team. It is not linked from the client-facing MCP page and is hidden from search.

Tools live
78
On the team token
66
Need the admin key
12

01Live today

78 tools in nine groups, pulled from the live connector on October 1, 2026. Anything badged Admin is refused on the team token.

Credits: create_microapp and retry_microapp cost 10, send_edit costs 1. Everything else is free.

A. Suites 9

A suite is one company's EXOS account: brand, credits, pages and hub. Start here to find one or make one.

  • create_suiteFree

    Provision a suite from a domain, same shape as signup: slug, 100 starter credits, brand pulled from Brandfetch. Dedupes by domain, so it hands back the existing suite unless you force a new one.

  • list_suites

    Newest suites with slug, company, domain, page count, credits left, suite URL and the comms channels they said they use.

  • search_suites

    Search every suite by company name or email domain. Not capped to recent ones, so use it when list_suites comes up short.

  • get_suite

    Full detail on one suite: brand, credits, every page with status and deep link, requestor role and priorities. Fuzzy-matches a name or domain if you don't know the slug.

  • list_suites_by_channel

    Suites whose customer uses a given channel (Slack, Outlook, WhatsApp). Handy for segmenting follow-ups by where their employees already are.

  • list_my_hubs

    Every hub a person can edit, owned or shared, with role and hub URL. Same logic as the account menu in the app.

  • add_creditsCapped

    Top up a suite's build credits. On the team token: 200 per call, 2,000 per rolling 24 hours. The admin connector is uncapped.

  • transfer_ownershipAdmin

    Hand a suite to a new owner by email. They get full control on next sign-in.

  • delete_suiteAdmin

    Permanently delete a suite and everything under it. No undo.

B. Pages and templates 9

The microapps inside a suite. Build from a gallery template or a prompt, iterate, publish.

  • list_templates

    Gallery templates you can build from, filtered by tag or free text. Capped at 100.

  • create_microapp10 credits

    Build a new page in a suite from a template or a prompt. Pass name to retitle a template build. Under 20 credits left, it asks you to confirm first.

  • get_build_status

    Where a build is: step, minutes elapsed, auto-retries, live URL once ready. Builds take a few minutes, so poll this.

  • retry_microapp10 credits

    Re-queue a build that failed before a project existed. Reuses the same row, never makes a second project.

  • send_edit1 credit

    Send an iteration prompt to a ready page. Changes land in the working copy, not live, until you publish.

  • publish_microappFree

    Push a page's current working state to its live URL. The step people forget after send_edit.

  • add_existing_projectFree

    Register a page built outside the EXOS queue. Always pass published_url, or you get a preview link nobody can use.

  • delete_microapp

    Remove one page from a suite and refund its 10 credits. The surgical alternative to deleting the whole suite.

  • set_template_visibilityAdmin

    Show or hide a template in the public gallery. Reversible.

C. Hub build and layout 21

The employee hub at /suite/{slug}/hub. Every tool here is free: tiles, layout, artwork and settings cost no credits.

  • bootstrap_hub

    Build a hub from what signup already knows: brand, the three priorities they picked, and their pages.

  • list_hub_section_sets

    The pre-built sections bootstrap_hub assembles, one per signup priority, with the wording each uses.

  • list_hub_layouts

    Ready-made hubs: onboarding, open enrollment, AI enablement, change and leadership, culture and recognition, everything.

  • apply_hub_layout

    Lay down a whole layout in one call: hero, quick links, tiles and extras. Pages the suite already has get linked, not rebuilt.

  • get_hub

    Read a hub: header settings and every tile with its id, archetype, link and audience. Call this before you change anything.

  • set_hub_settings

    Title, tagline, greeting and hero banner.

  • list_hub_archetypes

    Tile archetypes: what a linked page looks like on the hub (checklist, benefits window, poll and so on).

  • list_hub_library

    Library templates a tile can be built from, with the archetype each lands as.

  • recommend_apps_for_tile

    One to three library templates that fit a tile, the same list the editor's Link an app shows.

  • add_hub_tile

    Add one tile: a summary of a built page, a link, or a native card.

  • update_hub_tile

    Change one tile. Pass only the fields you want changed.

  • remove_hub_tile

    Delete one tile and close the gap. The page behind it is untouched.

  • reorder_hub_tiles

    Set tile order. Pass every tile id exactly once or the call is rejected.

  • summarize_hub_tile

    Fill a tile from the live published page it links to, never from the build brief.

  • generate_tile_image

    AI artwork for one tile, as a backdrop or a picture, applied in the same call.

  • list_hub_image_styles

    Picture styles available: photo, illustration, abstract, icon, plus any custom ones saved on the suite.

  • set_hub_image_styles

    Replace a suite's custom picture styles, up to six.

  • refresh_hub_logos

    Re-pull every Brandfetch logo variant for the hub's domain.

  • reindex_hub_pages

    Re-read the live text behind every tile so the hub's Ask assistant answers from what is actually published.

  • get_hub_settings_link

    Deep link straight into one settings section: brand, integrations, personas, chat log and more.

  • set_default_hubAdmin

    Set the hub a person lands on after login.

D. People, audiences and demo personas 9

Who the hub knows about and who sees what. The persona tools are demo data for walkthroughs, not real employees.

  • list_hub_people

    The hub's people directory: name, email, title, department, location, manager. Editors only.

  • upsert_hub_person

    Add or update one person in the directory, matched on email or name.

  • remove_hub_person

    Remove one person from the directory.

  • set_tile_audience

    Who sees a tile or section, by location, department or manager status. AND across dimensions, OR within one.

  • list_hub_personas

    Demo personas behind the View as switcher. Falls back to five defaults if none are stored.

  • set_hub_personas

    Replace the demo personas: name, title, team, location, language, roles, start date.

  • simulate_hub_event

    Fire a demo HRIS event for one persona (new hire, anniversary, promotion) so the hub shows its lifecycle banner.

  • get_manager_view

    The demo My team view a manager persona sees, with six sample direct reports.

  • list_hub_integrations

    External MCP servers wired into the hub (ChangeEngine comms or custom) and their allowlists.

E. Company research and personalization 6

Signup research feeds a rule engine that adds tiles like Refer a friend, Coming up and company news. Reading is open, rerunning rules is admin.

  • research_company

    Research a domain from public sources and save the facts. Dry run: never touches a hub.

  • get_company_facts

    Read saved facts for a domain or suite. Never runs research, never spends credits.

  • explain_personalization

    Why a hub looks the way it does: facts summary, which rules fired or skipped and why, planned tiles.

  • apply_personalizationAdmin

    Re-evaluate the rules on an existing hub. Dry run by default; live mode only touches rule-made tiles.

  • refresh_personalizationAdmin

    Re-run research and refresh rule-made tiles. Admin-edited tiles only get an Update available offer.

  • personalization_coverageAdmin

    Fleet view: how often each rule fires across hubs built since a date, and the top skip reasons.

F. Launch and comms 6

Turn a tile into a rollout. Everything here drafts or links; push notifications are the one thing that actually sends.

  • hub_tile_rollout_plan

    Step-by-step launch plan for one tile, with advice and the comms assets to send.

  • hub_tile_comms_prompt

    A ChangeEngine comms brief written from the tile's own content, ready to hand to the ChangeEngine MCP.

  • tile_comms_drafts

    Draft comms for one tile, one per channel: email, Slack, Teams and SMS, each linking back to the tile.

  • send_hub_notification

    Push a notification to everyone who turned notifications on for the hub. This one really sends.

  • create_hub_review_link

    A 30-day read-only review link for a CHRO or budget owner, with comments on.

  • list_hub_review_comments

    Review links with their state, and every comment reviewers left, newest first.

G. Invites and outreach 7

Get a hub in front of a prospect. Invite links are open to the team; anything that emails or texts someone is admin.

  • create_hub_invite

    A shareable link that builds a hub branded from the recipient's email domain when they click. Sends nothing. requested_by must be your @changeengine.com email, and the same email always returns the same link.

  • list_hub_invites

    Invites with status (created, clicked, building, built, claimed, expired), domain and who requested them.

  • send_claim_linkAdmin

    Email a prospect a magic link to claim a suite that was pre-built for them. The no-show play.

  • create_outbound_hub_linkAdmin

    A scanner-safe hub link for cold email, so link scanners don't trigger a build.

  • list_outbound_hub_linksAdmin

    Outbound links with bot versus human views and activation status.

  • send_smsAdmin

    Send one SMS through Twilio. 480 characters, 25 per rolling 24 hours, every attempt logged.

  • list_sms_logAdmin

    Recent SMS attempts and their delivery state.

H. Walkthrough videos 3

Attach a roughly one minute walkthrough to a suite page or a template.

  • add_suite_video

    Attach a walkthrough to a suite page. The server pulls the file from your URL and hosts it.

  • list_suite_videos

    Registered videos with views, plays and completes. Check it before adding a second one.

  • add_template_video

    Attach one walkthrough to a gallery template.

I. Analytics and listening 8

How prospects and employees actually use what you built. All read only, all free.

  • get_suite_analytics

    Views per suite and per page.

  • get_video_analytics

    Video views, split into suite overview and per-page videos.

  • get_hub_analytics

    Hub views against the prior period, unique visitors, card clicks, in-card actions, searches, click-through, employee versus admin split.

  • get_hub_insights

    The plain-language read: three-sentence summary, three highlights with numbers, three recommendations.

  • get_hub_search_recommendations

    What employees searched for, turned into up to five concrete things to add.

  • get_hub_push_stats

    Notification reach: subscribed devices by platform and how many installed the hub.

  • list_hub_tile_responses

    What employees submitted on interactive cards: nominations, questions, poll votes, RSVPs, referrals.

  • list_hub_chat_log

    Every Ask question and admin edit chat on the hub, newest first.

02Prompt library

Starter prompts that chain the tools the way a rep actually works. Swap acme.com for your prospect.

Find

Brief me on a suite before a call

Find the EXOS suite for acme.com. Tell me what pages it has, which are live, credits left, the priorities they picked at signup, and how many views the suite and its videos have had.
Find

Who uses Slack

List EXOS suites whose customer said they use Slack, created in the last 30 days, with the suite URL for each.
Build

Demo suite for a prospect

Create an EXOS suite for acme.com. Then show me the gallery templates tagged onboarding and recommend the two best fits for a 2,000 person company before you build anything.
Build

Retitle a template build

In the acme suite, build the Employee Onboarding Experiences template and name it Acme New Hire Hub. Check the build status every couple of minutes and give me the live URL when it is ready.
Build

Edit, then actually publish

On the Acme New Hire Hub page, change the hero headline to Welcome to Acme, you're going to like it here. Then publish it and confirm the live URL shows the new headline.
Hub

Stand up a hub in one pass

Read the acme suite's hub. If it is empty, bootstrap it from signup. Then show me every tile with its archetype so I can decide what to cut.
Hub

Explain the personalization

Explain how company research personalized the acme hub: which rules fired, which skipped and why, and what tiles it planned.
Hub

Demo the lifecycle moments

On the acme hub, simulate a new hire event for the first demo persona, then show me what the manager view looks like for their manager.
Outreach

Invite link for a prospect

Create an EXOS hub invite for jane@acme.com, requested by me (my @changeengine.com email), campaign q4-dinner. Give me the link only, do not send anything.
Outreach

CHRO review link

Create a review link for the acme hub so their CHRO can look and comment. Then, a week from now, I will ask you to list the comments.
Launch

Rollout pack for one tile

For the open enrollment tile on the acme hub, give me the rollout plan, then draft the email, Slack and Teams versions of the launch message.
Measure

Is anyone using it

Give me the acme hub's analytics for the last 30 days, the plain-language insights, and the top things employees searched for that the hub does not answer yet.

03Test drive the EXOS MCP

Four short tracks, about 40 minutes end to end. Expect to spend 10 to 20 credits on the build track.

  1. 1

    Install the exos-demo-factory plugin from the ChangeEngine plugin marketplace in Claude. It bundles the EXOS connector with the team token already set, so there is nothing to paste.

  2. 2

    Already have it? Disconnect and reconnect the EXOS connector, or restart Claude. Claude caches the tool list when it connects, so tools shipped since then stay invisible until you do.

  3. 3

    Confirm it worked. You should see real suites within a few seconds.

    List the 5 newest EXOS suites with their suite URLs.
  4. 4

    Need an admin tool (anything badged Admin below)? Those are refused on the team token. Ask Kes for the admin connector and add it as a second connector. Never put the admin key in a shared plugin or paste it into a doc.