Give an AI agent access

Mochi can work alongside an AI assistant. Once connected, it can look at your work items, change sets, configuration, and history, and, for any Aprimo instance you connect, help build configuration there. It acts as you. A change set it puts together always waits for a person to approve it, even when the workspace doesn't ask for approvals otherwise, and then goes through the delivery your workspace has set up.

Looking and changing are separate decisions

Turning AI access on lets an assistant read. It can see your configuration and its history, your change sets, work items, pipelines, and runs. That's all it can do to begin with.

Letting it make changes in Mochi is a second decision, and it starts off. With it off, you can point an assistant at a workspace to help you look into something without it putting a change set together or editing a work item. When an admin turns it on, the assistant can put together change sets and update work items, and those follow your normal review and delivery.

Changing a connected Aprimo instance is a separate choice again, set for each instance. An admin can connect one read-only, so an assistant can look but not change it, or read-and-write for the instance where the work gets done. So an assistant might build configuration in one instance while only looking in another, whatever the workspace change setting is.

Connect your assistant

There's one address to add, and you add it once. Find it on your AI accessscreen, reached from the workspace sidebar under Connect.

1. Copy the server address. On the AI access screen, copy the address shown under “How to connect.”
2. Add it to your assistant. In your AI assistant (for example Claude), add a new connection and paste in the address. Most assistants call this an MCP server.
3. Sign in to Mochi. The first time you use the server, your assistant sends you to sign in. That sign-in is what identifies you.

Signing in to Mochi is what makes the work-item and change-set tools available to your assistant.

Sign in to an Aprimo environment

Each Aprimo environment is a separate account, so you sign in to it on top of your Mochi sign-in. You only do this for the environments you actually use, and only once each.

1. Find it on the AI access screen. Every Aprimo environment in the workspace shows up there, along with whether an admin has turned on its AI access.
2. Choose Sign in with Aprimo. You sign in with your own Aprimo account. From then on, the assistant can work with that environment's configuration using your Aprimo permissions.

You can also let the assistant prompt you the first time it needs an instance: it'll hand you a sign-in link, and once you're signed in you carry on where you left off.

Some things stay a person's job

An assistant can't create or replace an access key. A key keeps working long after the conversation that made it is over, so handing one out is a person's call.

Approving is a person's call as well. An assistant can't approve a change set, whether it put that change set together or someone else did. It can't turn down someone else's change set either.

Delivery works the same way. An assistant can't send a release out, start a run again, stop one that's under way, or put an environment back to an earlier version. It can get everything ready and tell you what it would do next, and then you choose.

Turning access off

Access follows your account. If your membership is removed, or an admin turns AI access off for the workspace or for an environment, the assistant loses that access right away. You can connect again later the same way.

You can also disconnect one AI client on your own. Your account page lists the AI clients signed in to your account, each with a Disconnect button. Disconnecting one leaves your other clients alone, and that assistant has to sign in again before it can do anything.

For what the assistant can and can't do once connected, see What an AI agent can do.