Skip to contentSkip to main content
← Back to all posts

Local vs Hosted AI Memory: Choose the Right Vault Setup for MCP

Decide between local-only, provider-backed, and hosted AI memory. Compare MCP access, storage boundaries, permissions, and a 25-minute verification workflow.

Share by email

An AI assistant cannot find the note you edited this morning. You can open it in your browser, so it feels as though the assistant lost your memory. Often, the note and the assistant do not share an authorized path to the same storage location.

Before changing prompts, decide where your knowledge should live and which AI tools need it. A local-first vault, provider-backed vault, and hosted MCP-accessible vault solve different problems. None is automatically right for every project.

This guide offers a decision matrix, permission-first setup procedure, and acceptance tests. It is about where knowledge lives and how it becomes reachable, not which model is smartest.

Three questions to answer first

A durable AI-memory setup distinguishes:

  1. Identity: Which logical vault owns the note and its history?
  2. Storage: Where do content and attachments physically reside?
  3. Access: Which authenticated client can retrieve which records, under what permission?

These are different concerns. A storage provider is not a vault identity. OAuth authentication does not grant permission to every vault. Retrieval does not make a note an approved decision.

Phasoric's documented architecture treats a vault as one user-owned logical container with local storage and optional remote bindings. Attaching a provider should not create a second Personal vault; two distinct client vaults should not merge merely because both have the same display name. This is the governing design, not a guarantee that every legacy migration or multi-provider workflow is complete.

Compare the three setups

SetupWhere notes liveAI access boundaryBest fit
Local-onlyDevice-local browser workspaceIn-page tools with appropriate local access; not remote hosted MCPPrivate device work without remote AI retrieval
External-provider-backedLocal operational state and an explicitly connected Dropbox, Google Drive, or GitHub sourceEligible provider content through authenticated hosted MCP, with mapping and provider permissionsTeams already keeping Markdown with a trusted external provider
Phasoric Hosted-backedLocal operational state and an explicitly attached hosted storage bindingEntitled, authorized MCP clients access a mapped hosted boundaryMultiple external assistants needing the same scoped project context

These are storage choices, not promises that every provider, client, or synchronization pattern works identically. See the published MCP contract for transport, mapping, and entitlement details.

An important exception: device-encrypted content requiring keys that remain only on the device cannot simply be decrypted by the hosted gateway. Do not circumvent the security boundary to manufacture access.

Why local-first is not the same as remote access

A local-first editor can support work while an internet service is down. That does not mean ChatGPT, Claude, or a server automation can directly read its local database.

Phasoric documents distinct paths: hosted MCP for explicitly mapped internet-reachable sources and an in-page WebMCP adapter for an active local workspace. Hosted MCP uses an opaque mapping handle returned by the service; local tools use the local vault selector.

If a remote assistant cannot find a local-only note, don't ask it to search harder. Keep the note local and accept the boundary, or deliberately attach a supported, suitably authorized remote storage mapping.

For connection problems, see MCP Connected but Can't Find Notes?. The question here is different: choose the right boundary before troubleshooting it.

Choose by task, not by feature checklist

Private planning on one device. A journal, rough strategy, or sensitive brainstorming may remain local-only. The remote agent cannot retrieve it accidentally through a hosted mapping. Maintain an independent backup; device-local storage is not disaster recovery.

Development notes already in GitHub. An external-provider mapping may fit a repository-centered team. Confirm that the selected source is eligible for hosted reads. A GitHub account connection alone is neither a logical-vault mapping nor authorization to every repository.

Several AI assistants working on one project. A hosted mapping can expose reviewed context to authorized clients without synchronizing their entire conversations. Use source-backed decisions, audiences, and read scopes. See Sharing Project Context Between ChatGPT and Claude.

Consultants working across clients. Keep distinct client vaults or rigorously segregated scopes. Test both sides: Client A's permitted note should be retrievable; Client B's note should not. Use the client-isolation checklist for more tests.

The rule: expose the minimum knowledge needed by the minimum number of assistants.

A 25-minute setup and verification procedure

This is a user-operated procedure, not a claim that Phasoric performs an automated audit.

Minutes 0–5: inventory the logical vault

Write down the vault's owner, purpose, audience, active storage binding, and whether content may leave the device. Select a non-sensitive known note, an attachment, and a decision with verifiable status.

Do not treat a display name as the definitive vault identifier. Similar names are common across clients and workspaces.

Minutes 5–10: choose the boundary

Choose local-only, an attached provider, or Phasoric Hosted. If remote MCP is necessary, check supported providers and plan entitlements first. Review the security and governance contract: authenticated identity, active grants, mapping authority, and Context Scopes are separate.

If a source contains data that should never be exposed to the intended assistant, narrow the scope or keep it local.

Minutes 10–15: connect the intended source

For a hosted client, follow the MCP setup documentation. Authenticate through a supported method and discover the available mappings instead of inventing identifiers from folder names. Use the returned mapping handle. Confirm that any external provider connection has the relevant active read capability.

Never paste OAuth tokens, personal access tokens, or other secrets into prompts, screenshots, notes, or debugging logs.

Minutes 15–20: run positive and negative reads

Ask the client for a distinctive phrase from an approved test note and require an exact source locator. Then request a note outside the client's permission scope; confirm its contents are not disclosed.

Finally, request a deliberately local-only note from a remote client. A safe answer identifies the access boundary instead of inventing a quotation or silently uploading content.

Minutes 20–25: verify failure handling

Use an unavailable test source or disconnected test client. Can you distinguish a transport error, denied permission, and empty search? Record the failure code without sensitive content.

Write down the owner, allowed client, mapping, test date, and review trigger. For a fuller restoration exercise, use the vault backup and recovery drill.

Copy this access-decision record

A small Markdown record makes each connection auditable:

# Knowledge access boundary
Logical vault: Project Atlas
Owner: Project lead
Data class: Internal project notes
Storage: Local + explicitly mapped provider
Remote access needed: Yes, read-only
Authorized audience: Named collaborators
Exclusions: Credentials and customer exports
Positive test: [date + source locator]
Negative test: [date + denied scope]
Review trigger: New client or changed permissions

This is a review template, not an executable configuration. Enforce permissions through the product's real grants and mappings, then verify behavior.

Five common mistakes

MistakeBetter approach
Treating a cloud folder as a second logical vaultPreserve durable vault identity and inspect bindings
Assuming MCP connection means all notes are readableVerify mappings, grants, provider access, and scopes
Uploading everything to fix one missing noteExpose only the justified source
Treating an empty search as evidence of deletionCheck locality, authorization, and availability separately
Mistaking synchronization for recoverabilityKeep independent backups and rehearse restore

There is also a decision boundary beyond storage: Pulse detects meaningful changes, Strata governs confirmed decisions, and Forge governs consequential approved actions in Phasoric's documented model. A hosted mapping does not turn an unreviewed draft into policy or permit an agent to bypass approval.

What a successful setup proves

You should be able to identify the logical vault, its storage bindings, the clients authorized to read it, and what happens when a request falls outside the permitted boundary.

Good AI memory makes allowed knowledge reachable and prohibited knowledge predictably unavailable. Portability comes from durable notes with provenance and explicit authority—not from copying every conversation into one giant shared transcript.

Frequently asked questions

Can a remote AI agent read notes stored only in my browser?

Not through Phasoric's hosted MCP gateway. Local-only browser state uses the in-page WebMCP path; remote access requires an explicitly authorized, supported hosted or remote-provider mapping.

Does attaching cloud storage create a second Phasoric vault?

Phasoric's documented architecture treats attached providers as storage bindings for the same logical user-owned vault. Distinct client or project vaults remain separate even if their names match.

Can hosted MCP access every file in my connected provider?

No. The gateway requires an authenticated client, a permitted vault mapping, current provider read capability and scope, and applicable entitlement. Device-only decryption keys remain unavailable to the server.