Who can use this feature?
The Chili Piper MCP lets an Admin create users and rebuild their setup, or assets (licenses, workspaces, teams, personal meeting types and distributions), from an AI assistant such as Claude or ChatGPT, instead of configuring each page by hand.
The most common case is a change of Google Workspace or email domain. Chili Piper cannot move users from one Google Workspace to another, and it cannot change the domain of an existing user's email, so every user must be created again. With the MCP, that rebuild takes a few requests.
MCP not connected yet?
How do I connect Chili Piper via MCP?
Setup steps for Claude, ChatGPT, Cursor, OpenAI Codex and Gemini CLI.
🔗 For further details, check here How do I connect Chili Piper via MCP?
Copying one rep's setup?
Chili Piper Skills (AI recipes)
The user-copy Skill copies one user's workspace and team memberships, and optionally their licenses, to another user in one request.
🔗 For further details, check here Chili Piper Skills (AI recipes)
Table of Contents
- Before you begin
- What you can create with the MCP
- Rebuild users after a domain change
- Limitations
- Related articles
Before you begin
- The Chili Piper MCP is connected to your AI assistant. See How do I connect Chili Piper via MCP?;
- You are a Super Admin in Chili Piper. A Workspace Admin can build inside the workspaces they manage, but cannot add users or assign licenses;
- Your organization has a free seat for every license you plan to assign. Old accounts keep their licenses until you deactivate them, so plan seats for both. Seat counts show at the top of Command Center > Users;
- You have the list of users to create, with their new email addresses;
- If your organization signs in with SSO (for example Okta or Microsoft Entra ID), your identity provider sends the new email addresses. Otherwise, the new users cannot log in.
What you can create with the MCP
The MCP covers almost every step of setting up a user. The two exceptions are the calendar connection and the Salesforce user link.
| What | What the MCP does | Good to know |
|---|---|---|
| Users | Creates the account, with its role, licenses and workspaces. | No invite email is sent unless you ask for one, so you can create users in bulk and invite them later. |
| Invitations | Sends the invite email to users who have not been invited yet. | An invite email cannot be unsent. |
| Licenses | Sets each user's product licenses. | A license is granted only when a seat is free, so read licenses back after each change. An update replaces the user's full set of licenses: list every license the user keeps. |
| Workspaces | Adds users to a workspace. | Users who are already in the workspace are skipped. |
| Teams | Adds users to a team. | Users are also added, with a weight of 100, to every distribution that uses the team, including existing ones. |
| Profile | Sets name, job title, time zone, working hours and User URL (the personal booking link). | Changing a User URL breaks every link that used the old one. |
| Personal meeting types | Creates the user's own meeting types (booking pages). | The link of each meeting type is generated automatically and cannot be changed. |
| Distributions | Sets who receives meetings, and their weights. | After you add users to a team, check the weights before you change them. An update replaces the full list of members, so ask the assistant to keep the other members as they are. |
Rebuild users after a domain change
After a domain change, each old user (jane@oldco.com) gets a new user (jane@newco.com) with the same setup. Both accounts sit in the same Chili Piper organization, and the old account stays active until you deactivate it.
Run the steps below in order. You can paste each example prompt into your assistant as written.
Step 1: Create the new users without inviting them
Ask your assistant:
Create a new user jane@newco.com with the same role, licenses and workspaces as the existing user jane@oldco.com, and do not send an invite yet.The old address only tells the assistant which account to copy. Then ask the assistant to read back each new user's licenses: a license is missing when no seat was free. To fix it, free a seat or add licenses in Command Center > Users, then ask the assistant to grant the missing license.
Step 2: Copy team memberships
Ask your assistant:
Add each new user to every team their old account belongs to.Note: The
user-copySkill copies one user's workspace and team memberships, and optionally their licenses, to another user in a single request. See Chili Piper Skills (AI recipes).
Step 3: Check distribution weights
Ask your assistant:
Show me the weights of the old and new users in every distribution.Adding a user to a team already adds them, with a weight of 100, to every distribution that uses the team. To see which distributions those are, go to Teams in the workspace, open the team and select the Used In tab.
Then ask for exact weights, not an increase. An increase is added to the current weight, so asking for "+50" on a weight of 100 gives 150.
In the Sales Team distribution, set jane@newco.com to 50 and jane@oldco.com to 0, and keep every other member and weight as it is.Step 4: Recreate personal meeting types
Ask your assistant:
For each new user, recreate the personal meeting types of their old account, with the same name, duration and location.The new meeting types get new links. Links already shared for the old meeting types do not move to the new user.
Step 5: Move the User URL to the new user
Ask your assistant:
Change the old user's User URL to jane-old, then give the new user the User URL the old account had.A User URL belongs to one user at a time, so the old account must release it first. The personal booking link does not work between the two changes, so make both in the same request.
Step 6: Send the invites
Ask your assistant:
Send the Chili Piper invite to the new users.Step 7: Connect calendars and Salesforce
The MCP does not do this step:
- Each new user logs in to Chili Piper and connects their calendar;
- An Admin links each new user to their Salesforce user, one user at a time.
When the new users work as expected, deactivate the old accounts in Command Center > Users to free their seats.
Limitations
- An existing user's email cannot be moved to another Google Workspace or domain, so new users are always needed. To change only the name part of an email on the same domain, see How to Change your Email in Chili Piper;
- The MCP does not connect calendars. Each user logs in and connects their own;
- The MCP does not link users to Salesforce. An Admin links each user separately;
- The link of a personal meeting type cannot be kept: it is generated automatically and cannot be changed. Only the User URL can move from the old user to the new one;
- License and distribution updates replace the whole configuration, so anything left out of the request is removed;
- Invite emails and User URL changes cannot be undone, and the MCP cannot delete users;
- If your organization uses SSO (for example Okta or Microsoft Entra ID), your identity provider must send the new email address, or the new users cannot log in.
Related articles
- How do I connect Chili Piper via MCP?;
- Chili Piper Skills (AI recipes);
- How to Change your Email in Chili Piper;
- How to set up your Identity Provider (IdP) SSO for Chili Piper.
Comments
0 comments
Please sign in to leave a comment.