How to Fix an MCP Server Returning the Wrong Information

The server is not wrong in the abstract. It cited a passage, or the client never asked it and wrote an answer anyway. Those feel identical until you open the link.

Copy the question exactly, and the URL in the reply. Then decide which case you are looking at. Each one has a different edit. Doing all three is how you lose the comparison.

What the three cases are

No citation. The client answered on its own. Enable the server in that chat and ask again. Look for a tool call.

The wrong page. The heading of the page you wanted does not use the words in the question, so a neighboring page keeps winning.

The right page, the wrong sentence. The document is what was retrieved. The sentence on it is the problem.

If you are not sure the server was called, start with Debug an MCP server. Why a near miss still looks like an answer is Choosing the right context.

Why you change one thing

A launch blog and a help center can both sound official. The blog says "replace the key promptly." The help center says overlap the keys for 24 hours. Prefer the help center, or disconnect the blog if it is not a source of truth.

Rephrasing until it passes teaches you a prompt. It does not tell you whether the page is fixed. Ask the identical question after the one change.

Deleting the server and starting over with the same documents cites those documents again.

Fix it in MCP Studio

MCP Studio is the no-code builder on Appa Tools. Open the server on the dashboard.

1. No citation. Turn the server on in that chat. A private server with a missing token never gets this far. See isn't connecting.
2. Wrong page. Rename the heading or put the reader's words in the first lines, then refresh the source. That edit is Make your documentation AI-ready.
3. Right page, wrong sentence. Fix the sentence. A retrieval change will not correct a typo, and it will not invent the 24 hour overlap if the help center never stated it.
4. Old source winning. Prefer the help center with a retrieval rule, or disconnect the blog. Rules are in the retrieval rules guide. Disconnecting deletes the indexed text from that source.

A tool mismatch is quieter. Question answering cited a guide when you needed the reference. Turn on API reference lookup and re-ask. See the tool guide.

Action analytics, Core plus Action at $99 a month, shows the page, section, and excerpt for each request, so you are not reconstructing the citation from the chat. The free tier still shows which source and tool ran. Prices are in What the questions people ask your docs can tell you.

Check that it works

Ask the same key rotation question again. The citation should be the help center, and the reply should include the 24 hour overlap. Open the page.

If it is still the wrong page

Make one more change, not three. Then ask again. Scoring a list of these questions is Measure MCP retrieval quality. A fluent answer with no citation at all is Reduce hallucinations with better MCP context.

Fix one wrong answer today

Open the server in MCP Studio, copy the question and the link, and pick one case. Change that one thing. Ask the same question again. Keep the edit when the citation matches the page you wanted.

Where to go next

• Retrieval rules
• Choosing the right context
• Make your documentation AI-ready
• Choosing tools