MCP Connected but Can't Find Notes? A Troubleshooting Guide

MCP Connected but Can't Find Your Notes? A Troubleshooting Guide

Your AI assistant reports that its MCP connection succeeded. It can see tools. Yet a search for a note you know exists comes back empty. This does not necessarily mean the note was lost.

Connection, authentication, source discovery, authorization, and retrieval are separate checks. A working network connection cannot guarantee that an agent is looking in the right place or has permission to read a particular document.

The following procedure uses Phasoric's documented hosted MCP gateway as a concrete example. Other MCP knowledge providers may use different tool names, permissions, and storage models.

Diagnose the symptom before changing settings

An empty search result applies to one request against one allowed source. It is not proof that the content does not exist anywhere.

1. Confirm that the MCP client authenticated to the right service

Phasoric publishes its hosted MCP resource at https://phasoric.com/api/mcp. Its developer reference documents Streamable HTTP and account OAuth for compatible interactive clients. A manual bearer token is an alternative for environments that cannot complete the OAuth flow.

A successful Phasoric website sign-in does not guarantee that the separate AI client has a valid MCP grant. Ask the client to discover the server's tools. If tool discovery fails, fix transport or authorization before testing note search.

Check whether the connection was revoked, the token expired or the wrong service endpoint was configured. Never paste live credentials into a prompt or support ticket. Record the time, client type and error message, with secrets redacted.

2. Run list_vaults instead of guessing a source

In Phasoric, the hosted list_vaults tool returns the mappings available to the authenticated account. Each mapping has an opaque identifier. Use its returned mappingId unchanged; do not infer one from a folder name, project title or an older screenshot.

This is especially important if you maintain personal, work and client vaults. Searching a permitted personal mapping cannot establish whether a note exists in a separate project mapping.

Compare the list with where the note actually lives. If the expected mapped source is absent, diagnose mapping setup or provider access. Do not keep adjusting the search query.

Test: Select a non-sensitive note in an accessible mapped vault containing an unusual phrase, such as a distinctive project code followed by two ordinary words. Search that exact phrase, rather than a vague topic like “planning.”

3. Distinguish local-only notes from hosted content

Phasoric is local-first. Its browser workspace can contain notes that have not been published or synchronized to an internet-reachable source. The hosted MCP gateway does not automatically read local-only browser state.

The documented hosted gateway supports explicitly mapped Phasoric Hosted content and eligible external-provider mappings, including Dropbox, Google Drive and GitHub. Local-only workspace tools operate through the in-page WebMCP path instead.

If a note exists only on your device, a hosted MCP search may correctly return nothing. A different prompt cannot cross that boundary.

Device-encrypted content can create a related limitation: if the decryption key never leaves the device, hosted services cannot simply open those encrypted bodies. This is a deliberate privacy boundary, not evidence that search is malfunctioning.

Before changing tools, answer one question: Is this note actually available in the mapped source and transport I am querying?

4. Check Context Scope permissions

A vault mapping identifies a source. A Context Scope governs which information is eligible for a particular agent, workspace, project or audience. These permissions are not interchangeable.

Phasoric's documented semantic MCP operations require an explicit contextScopeId, and hosted authorization is checked again when persisted intelligence is read. A team scope does not simply expose every participant's private notes. A narrower session or project scope may deliberately exclude a resource that remains available elsewhere in the account.

Use a controlled test:

1. Identify the mapping returned by list_vaults.
2. Select a Context Scope that should include the test note.
3. Try a clearly permitted source.
4. Compare it with a source that the scope intentionally excludes.

If the excluded source stays hidden, the boundary is working. Do not “solve” a missing note by turning off authorization controls or giving an agent global access.

5. Separate finding a note from reading it

For a scoped, accessible mapping, try a two-step read. First use search_notes with a distinctive query. If the tool returns a candidate path, use get_note_content on that exact path.

These tests answer different questions. Search concerns discovery; a direct note read concerns access to a specific source and revision. A search result can become stale after a file moves or a provider changes permissions. Conversely, an authorized direct read might succeed when the search phrase does not match.

Compare the returned content and revision with the expected source. If they differ, inspect source synchronization and provider state before concluding that the language model is at fault.

Avoid assuming every tool uses the same argument shape. Follow the current tool schema, particularly for hosted mappingId versus local vaultId.

6. Look for partial results and provider limitations

Knowledge connectors often bound search results, file traversal, request duration and provider access. A client may summarize a response as “no notes” even when the underlying tool reports a partial result, an unavailable source or a permissions error.

Inspect the raw tool outcome where your client makes it available. Check for pagination cursors and omitted-source reasons. Continue with a returned cursor when supported; do not construct an arbitrary cursor or infer that an incomplete result exhausts the vault.

External provider connections deserve their own check. An active Google Drive or Dropbox account connection is not blanket permission for every folder. Phasoric's hosted implementation checks both the specific mapping and the account's active provider connection with the needed capability.

If previously visible material disappears, verify the provider connection, mapping location, file access and ownership. Leave write permissions off during a read-only investigation.

7. Verify the knowledge is current—not just retrievable

Finding an old decision accurately can still produce an incorrect recommendation. If an assistant retrieves a document recommending a retired API, the retrieval step worked while the reasoning may be unsafe.

Where available and authorized, Phasoric documents semantic operations such as get_decisions, get_decision_evidence, get_changes and get_contradictions. The appropriate sequence is to retrieve the relevant decision, inspect its supporting evidence, and determine whether later evidence superseded it.

Ask: “Which decision currently applies? What source supports it? What changed since the older record?” If the system cannot establish the answer, it should identify that limitation rather than manufacture certainty.

Also note that unpublished local intelligence is not automatically available in hosted MCP. A missing hosted decision or living brief does not prove that no local record exists.

8. Capture a reproducible, privacy-safe report

If the issue remains, capture a small diagnostic record:

• AI client and connection type, excluding passwords and tokens.
• Time, operation name and the actual error or result category.
• Whether tool discovery and list_vaults succeeded.
• Mapping type and redacted identifier.
• Whether the note is local-only, hosted or provider-backed.
• Context Scope used, redacted as appropriate.
• Whether a distinctive search and direct authorized read differed.
• Any pagination, partial-result or permission indicator.

A report with these facts helps distinguish authentication, mapping, authorization, provider and search problems. It is much more useful than “MCP is broken,” and it does not require exposing private note contents.

A reliable baseline for AI agent memory

Before pursuing complex cross-agent workflows, establish one verified path: connect → discover the mapping → select the scope → search for a known note → read it → check its source and revision. Repeat that test after changing clients or provider permissions.

Do not enable writes simply to validate reads. Phasoric's documented write tools distinguish previews, approval and application, and its semantic proposal operations do not themselves authorize consequential actions.

The end goal is not merely a green “connected” indicator. It is an assistant that can retrieve the right permitted evidence, recognize its limits, and explain what it used. That is the foundation for dependable context across AI tools.

Continue with the Phasoric MCP documentation, or see how AI agent memory with Phasoric connects reviewed project knowledge to compatible assistants.