Rose MCP: fix what your agent says from Claude or ChatGPT

When a client reports a bad answer, an agent at Rose picks it up. It reads the conversation, works out what caused the answer, prepares a fix and tests it on the client’s agent.

It didn’t start that way. Corrections used to reach us in spreadsheets. We moved them into the conversation, as ratings, because a rating carries the conversation and the knowledge behind the answer. Then we gave that queue to an agent. In our build-or-buy post we called this corrections from feedback, and said that keeping a website agent right is a few hours of work every week, forever.

But some corrections shouldn’t have to go through us at all. You know your offer changed before we do, and one client told us in September that it wanted more control over its answers.

So since October, a Rose client can connect Claude, ChatGPT, Claude Code or Codex to their account and make the correction themselves. Rose then retrains their agent and updates its knowledge automatically, and their assistant tests an FAQ change the same way our agent does. Here is what it does.

You tell your assistant what is wrong

Our FAQ on onboarding is outdated: it’s now included in every plan. Show me the change, then retest the question.

The connection uses MCP (Model Context Protocol), an open standard that lets an assistant use an outside service. Rose publishes a list of tools, and your assistant calls the ones your request needs and shows you each call. You only set it up once.

Your assistant can search, read, add, edit and delete your FAQs and the documents you uploaded, and hide an FAQ without deleting it. It finds the FAQ, writes the correction and stops there. Nothing is saved yet. It shows you a before and after, like this one (the text is an example):

--- FAQ (current)
+++ FAQ (proposed)
@@ -1,4 +1,4 @@
 Q: Does the Starter plan include onboarding?
-A: No, onboarding is a paid add-on.
+A: Yes, onboarding is included in every plan.
 Topic: pricing
 Enabled: True

You try it before anyone else sees it

The wording may look right, but what matters is what your agent will say to a buyer. So your assistant can ask your agent the question as if the change were already saved, and you read the answer.

These questions run as Playground tests: they count in neither your analytics nor your plan usage.

You confirm

The connector instructs your assistant to apply a change only after you confirm it. Once you do, Rose saves the FAQ and retrains your agent automatically, so its knowledge is updated within a few minutes. If someone edited that FAQ after your preview, the change is refused and your assistant has to preview it again, so you never overwrite a colleague’s fix without seeing it.

Your assistant can check when the retrain has finished, then ask the question one more time, so you can compare the answer with what you expected.

When the facts are right and the answer still isn’t

In October, a visitor wrote to one client’s agent in French, asking whether the company could interview nurses in Spain. The agent’s answer was correct, and it was in English.

No FAQ fixes that, so the report came to us and was closed two days later. Your assistant can file that kind of report too:

That answer was right, but it should have been in French. Report it.

Your assistant reads the conversation, identifies the exact answer and asks what it should have said if that is unclear. The report carries the visitor’s question, Rose’s answer, your expected answer and a link to the conversation. For a problem with no conversation behind it, your assistant can open a general support ticket instead.

Either way, you check the workspace, your email and the full report before it is submitted. The ticket then appears in Support in your backoffice, and answer reports join the queue our agent works through.

Who controls what

You sign in as yourself. There is no key to copy: you sign in with your Rose account and allow the connection. Your assistant then sees the websites and data you see in the backoffice, and no more. To disconnect it, remove the connector in your assistant’s settings.

The confirmation happens in your assistant. Rose checks that a change comes from a recent preview made by your account. It cannot check what your assistant showed you or whether you approved it, and there is no separate approval step in the backoffice. So read the diff, and approve the apply_change tool only once you have. It is the only tool that saves a change or submits a ticket.

What your assistant reads leaves Rose. It goes to your AI provider under your account’s terms with them, like any document you share in a chat.

What it does not change

Your assistant works on your FAQs and uploaded documents. It does not change your agent’s settings, such as its tone or calls to action, your website’s pages as Rose scanned them, or your GEO pages.

Connect your assistant

1. In the Rose backoffice, open Integrations > AI assistants and select Claude & ChatGPT.
2. Copy the Connection prompt and paste it into your assistant.
3. Follow its guidance. In Claude or ChatGPT, you may need to add the Connector URL from the same panel yourself.
4. Sign in with your Rose account and allow the connection.
5. Ask your assistant to list your Rose workspaces, to check that it worked.

Your assistant may need your workspace administrator to allow custom connectors first. The client guide has every tool and its parameters, and what to do if something goes wrong.