Skip to main content
Use this page when SeekOut MCP behaves unexpectedly in your AI assistant. For assistant-specific setup issues, see the connection guide for your assistant.

​
Result counts differ between your assistant and SeekOut

Your assistant may report one candidate count while the shareable link or Recruit workspace shows a different number, including zero. Check the following causes in order.

​
The workspace opened in Smart Match view

Workspaces can open in Smart Match view, which shows a broad ranked pool that can be much larger than your filtered result. Switch the workspace to Boolean view to see the exact results that match the search your assistant built.

​
An ATS pipeline search is not attached to the workspace

When your conversation searches your ATS pipeline and then saves candidates to a workspace, the workspace attaches the public talent search, not the ATS search. The saved candidates are still in the workspace, but re-running the workspace search queries public data, so its count differs from the ATS result your assistant reported.

​
Filters did not carry over

If the workspace or shareable link shows zero results, ask your assistant to list the data source, query, and filters it applied, and compare them to what the workspace shows. In the workspace, clearing and reapplying power filters can restore the expected results.

Show me the data source, query, and filters used for this result, and give me the shareable search link.

If the counts still do not match after these checks, contact SeekOut Support with the shareable link and the criteria your assistant reported.

​
An error appears, but the search keeps working

SeekOut MCP includes a built-in verification step that asks your assistant to double-check that search results make sense before presenting them. Some assistants display this step as an error message even though nothing failed. If you see an error while results are still being produced:
  • Let the assistant continue working through it. The verification step resolves on its own.
  • Do not restart the conversation. Starting over loses the search state your conversation has built.
  • If you want to confirm the results yourself, ask the assistant for the search links it used.

​
Connection problems

​
”Unable to reach SeekOut App” in Claude

This usually indicates a stale Claude desktop app rather than a SeekOut outage. Restart the desktop app and install any pending update, then retry. See Claude troubleshooting for other Claude-specific issues.

​
Interactive SeekOut buttons or UI do not appear

If your assistant supports interactive MCP app views but SeekOut results render as plain text, disconnect and reconnect the SeekOut connector in your assistant’s settings.

​
Your assistant keeps asking you to approve SeekOut tools

Claude prompts for tool approval per tool, and the setting is per user. See Claude troubleshooting to pre-approve SeekOut tools. Other assistants do not currently expose this control.

​
Get more help

If an issue persists, contact SeekOut Support or your SeekOut account team. Include what you asked, what happened, and what you expected, plus the shareable search link when the issue involves search results.