An MCP memory server with explicit boundaries
Expose the project knowledge your agent needs through a documented MCP connection. Choose the vault, scope the access and review changes before they are applied.
Premium includes 2,000 MCP operations and 25,000 hosted-intelligence credits per month.
A documented read → review → write contract
Discover
list_vaults
Use a returned mapping handle; respect its read and write permissions.
Retrieve
search_notes → get_note_content
Find the relevant record and inspect its path and provider revision.
Preview
preview_note_writes / preview_note_deletions
Show the proposed change. Reads do not authorize writes.
Approve, then apply
apply_note_writes / apply_note_deletions
Apply the approved preview with an idempotency key and the current hash for an existing note.
Ask for context before action
“Find the current sync decision in my authorized project Vault. Read the note and return its path. Do not change anything.”
The client discovers permitted mappings, searches one vault and reads the matching note. Returned source context lets you check the rationale before planning a change.
A compatible client can retrieve the project record when asked, instead of relying on what fits in one conversation. Your notes remain the source of truth.
Discover authorized vaults, search paths and bounded content, and read a note with its provider revision. Supported tools also expose source-linked graph, schema and provenance context.
Preview supported note creation, append and transaction changes. Application requires approved intent, write scope, mapping permission, duplicate-request protection and revision checks for existing notes.
Inspect the example
Fictional project, prepared sources and review. These controls reveal the example; they make no AI requests, save no notes and grant no permissions.
Atlas/Decisions/014-import-queue.md
Revision: synthetic-v1 · Recorded: 2026-09-01
Keep imports asynchronous so a browser closing does not interrupt the job. Retain the original upload for seven days. Reuse a stable job key when retrying. The seven-day retention period is an assumption to review if storage policy changes.
Question: Can I replace the queue with a longer browser timeout?
Expected observation: A retention change does not remove the need to survive a browser closing. Cite both sources, preserve the queue requirement and flag the unresolved recovery question.
Excluded: an unrelated project launch note. These expected observations are authored examples. No retrieval algorithm, authorization boundary or model was executed to produce them.
The public MCP reference describes authorized mappings, decision evidence and write previews. Documentation explains the contract; the prepared example above is not a connected test or a measured result.
Durable context. Deliberate access.
Phasoric exposes the knowledge you authorize. It does not silently ingest every conversation or automatically remember everything your agents do.
Inspect the MCP boundariesHosted MCP reaches explicitly mapped Phasoric Hosted, Dropbox, Google Drive or GitHub vaults. Local-only vaults and device-encrypted remote bodies remain unavailable.
Ask for the note path, evidence and limits of the answer. Your Markdown remains portable across tools.
Review a proposed note change before application. Write permission, current-content checks and duplicate-request safeguards still apply.
Documented client setup
An authenticated Vault read was verified in Codex. The other guides describe documented setup paths; client plans, versions and workspace policies determine availability. They do not establish Phasoric interoperability for every client version.
Prepare your vault and verify a first readOpenClaw, Hermes Agent and Grok document remote MCP connection paths. These guides map those instructions to Phasoric; authenticated interoperability has not been verified for these clients.
The agent authenticates to Phasoric. Dropbox, Google Drive and GitHub credentials are managed separately. Start with a permitted read, then inspect the mapping’s write authority before proposing changes.
See the real Codex workflowExplicitly mapped, internet-reachable Phasoric Hosted, Dropbox, Google Drive and GitHub vaults. A provider connection alone does not expose its folders. Local-only vaults and device-encrypted remote note bodies remain unavailable.
Note writes preview by default. The client should show the proposed content and apply only after your approval, using dryRun=false and the required safeguards. Supported consequential external actions proposed through Forge have their own approval boundary.
No. Remote-provider writes need an explicit grant for the exact mapping, a non-pull mapping direction and provider file-write capability. Client automation settings do not replace these checks or your approval.
Hosted MCP starts with Premium at $14.99/month, including 2,000 MCP operations per month. Higher plans increase allowances and features. Free credit packs do not enable MCP.
Start with one project
Keep the brief, recover the evidence and save the reviewed decision. Choose how you want to use that context.
Connect the AI tools you already use to your authorized Phasoric knowledge. Hosted MCP starts with Premium.
$14.99/month includes 2,000 MCP operations and 25,000 hosted-intelligence credits each month. Higher plans increase limits and features.
Connect my AI toolsNo MCP setup required. Ask Phasoric directly using hosted intelligence with bounded relevant source context.
Eligible Free hosted accounts can buy 50,000 credits for $5.99. Usage is metered; a credit pack does not enable MCP.
Try hosted intelligence