Skip to main content

An MCP memory server with explicit boundaries

Give your agent context. Keep control of access.

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

  1. Discover

    list_vaults

    Use a returned mapping handle; respect its read and write permissions.

  2. Retrieve

    search_notes → get_note_content

    Find the relevant record and inspect its path and provider revision.

  3. Preview

    create_or_append_note / apply_note_transaction

    Show the proposed change. Reads do not authorize writes.

  4. Approve, then apply

    dryRun=false

    Use an idempotency key and the current hash for an existing note.

Ask for context before action

One question. A traceable source. No blanket access.

“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.

  1. 01

    Why MCP for durable context?

    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.

  2. 02

    What can be read?

    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.

  3. 03

    What can be written?

    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.

Durable context. Deliberate access.

Keep control of the record.

Phasoric exposes the knowledge you authorize. It does not silently ingest every conversation or automatically remember everything your agents do.

Inspect the MCP boundaries
  • Choose the source

    Hosted MCP reaches explicitly mapped Phasoric Hosted, Dropbox, Google Drive or GitHub vaults. Local-only vaults and device-encrypted remote bodies remain unavailable.

  • Keep the provenance

    Ask for the note path, evidence and limits of the answer. Your Markdown remains portable across tools.

  • Approve the write

    Review a proposed note change before application. Write permission, current-content checks and duplicate-request safeguards still apply.

Documented client setup

Start in the tool you already use.

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 read

More remote MCP setup paths

OpenClaw, 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.

Provider credentials stay with Phasoric.

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 workflow

Before you begin

What does hosted MCP expose?

Explicitly 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.

Where does approval apply?

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.

Does read access permit a write?

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.

What plan is required?

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

Give the next session something to build on.

Keep the brief, recover the evidence and save the reviewed decision. Choose how you want to use that context.

Use it through MCP

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 tools

Use hosted intelligence

No 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