← Help center

AI assistant access (MCP)

What the setting allows

AI assistant access (MCP) is a workspace setting in Admin → Developer. When it is on, owners and admins of the workspace can consult on it from their own Claude or ChatGPT account: the assistant reads the workspace's setup, metrics, and campaigns the way the Yapper consultant does, and can prepare proposed changes.

A proposed change never updates your workspace by itself. It waits in the dashboard until an owner or admin reviews and approves it, the same as a Consultant proposal. See consultant-proposals.

AI assistant access is separate from Consultant access. Turning one on or off does not change the other. AI assistant access does not draw down your Yapper credits; the conversation runs in the team member's own Claude or ChatGPT account.

Members never get AI assistant access, whatever this setting says.

What leaves Yapper

Everything the assistant reads while connected goes into the team member's own Claude or ChatGPT account and is kept there under that account's settings, outside Yapper. That includes your customers' messages when the assistant reads a conversation to explain a reply, and your team list (names, emails, roles, and access) when it looks at who can reach what. The assistant reads only the conversations that team member can open in their own Inbox: when an admin's access in Admin → Team hides a conversation from them, their assistant cannot read it either. The team list is the one they see in Admin → Team. Once the assistant has read something, Yapper cannot delete it from their account.

Before you turn the setting on, make sure your team is comfortable with customer conversations being read in their personal or company Claude or ChatGPT accounts.

Turn AI assistant access on or off

Only the workspace owner can change the setting. Open Admin → Developer, find AI assistant access (MCP), and select the checkbox. Turning it on asks you to confirm that you understand what the assistant can read. Admins see the setting but cannot change it.

AI assistant access is off until the owner turns it on.

Connect your assistant

Once the owner has turned AI assistant access on, each owner or admin connects their own assistant. The Yapper server address is:

https://mcp.yapper.chat/mcp

Signing in opens a Yapper page that names the site you will return to and asks for your work email. Continue only if you just started connecting from your own assistant. The page then sends you to the same sign-in you use for the dashboard, with Google or your company's single sign-on if that is how you sign in. Afterwards you return to your assistant, which can then use the Yapper tools and read the help center. Finish signing in in the browser window that opened the Yapper page; if sign-in says the request was started in a different browser, start connecting again from your assistant. A connection stays signed in while you use it. If you don't use it for 30 days, or a year has passed since you signed in, your assistant asks you to sign in again.

The assistant works on the workspace your Yapper sign-in belongs to. It reports that access is turned off, or that your role does not allow it, when either is the case; ask the workspace owner.

Approve a change the assistant prepared

When the assistant prepares a change, it gives you a link that opens the proposal in the dashboard's review window, the same one used for Consultant proposals. There an owner or admin approves it, rejects it, or leaves a comment. If you are not signed in, you sign in first and the proposal then opens.

The assistant does not see your decision on its own. Ask it to check on the proposal and it reports whether it was approved, rejected, or commented on. It can also see the workspace's other proposals, including ones another admin or the dashboard Consultant prepared, so it can build on them instead of repeating them.

If the link says the proposal was not found in this workspace, it was prepared for a different workspace than the one you are signed in to. Sign in with the email you use for that workspace. If it says only owners and admins can review proposed changes, ask an owner or admin to open the link.

Revoke access

Turning AI assistant access (MCP) off ends AI assistant access for everyone in the workspace on their next request. Proposals already prepared stay in the dashboard for review.

To end one person's access, remove them from the workspace or change their role to member in Admin → Team. That takes effect on their next request. See team-roles-and-access.

If your team signs in with Google or your company's single sign-on, AI assistant access does not appear in that provider's list of connected third-party apps, and removing it there has no effect. The setting and roles in Yapper are how you control it.