When your agent says it cannot find your notes
The connection worked, the tools are listed, and the agent still answers that it cannot find anything. This is the most common first-day problem, and it is almost never the connection.
Almost always it has no memory bullet assigned, or the branch is outside what it reaches, because its key was made without the whole outline or you let it reach only one bullet. Both search tools name the roots they walked, so read that line before you look anywhere else.
Set it up
- Point the client at https://pando.ink/mcp, which speaks streamable HTTP.
- Authenticate with OAuth 2.1 and dynamic client registration, or paste a key from Agents and API keys as a Bearer token.
Check one: does it have a memory bullet
Ask the agent to call whoami. The answer carries memoryRoot, and when that is null the agent has no bullet of its own, so remembering is refused outright rather than written somewhere you would never look. Assign one on the agent’s row under Agents and API keys and ask again.
Check two: is the branch inside what it reaches
A connector you approved starts with your whole outline, so for a connector this can be the cause only if you have pressed Let it reach only on its row: it then reaches that bullet and what is under it, and nothing else. An agent made with “Let it read and write this outline” unticked reaches the memoryRoot from check one and everything under it, plus any bullet it remembered in before, and no amount of searching will find a branch outside those, which is the behaviour you chose when you made it. To give either of them that branch, zoom into it, open the agent’s row under Your agents in Agents and API keys, and choose Remember in “…”, the bullet you are in.
Why a zero here is a real zero
When recall or search finds nothing, the answer echoes the roots it actually walked. So an empty result says where it looked, not just that it looked. That is the difference between "your note is not in the places I can reach" and "your note does not exist", and only the first one is ever true here.
Two smaller causes, worth a look
- The key was revoked. The refusal says revoked rather than a generic failure, so the reason is in the error text.
- The client cached the tool list at session start. A tool added since then is not offered until the session restarts, which looks exactly like a missing feature.
Deeper
Connect an agent, about two minutes · The twelve tools · Which note apps an agent can reach · Who runs this