Set up your AI agent
Give your agent access to the knowledge behind your work. Start with one project and one read. See the workflow, or read the MCP protocol reference.
1. Prepare your Phasoric vault
- Sign in to your Phasoric account. Hosted MCP is included from Premium upward, with plan-specific usage limits. Compare plans.
- Choose a Phasoric Hosted vault, or connect Dropbox, Google Drive, or GitHub and explicitly map the folder/repository containing your notes. A provider connection alone does not expose a vault.
- Confirm the note you want to test is accessible through that mapping. Local-only browser vaults and device-encrypted remote bodies cannot be read through hosted MCP.
- Start with read access. Enable a mapping's MCP write permission only if you want that client to propose and apply approved changes. External-provider writes also require a non-pull mapping and the provider's file-write capability.
2. Choose your client
Use this same public Streamable HTTP URL in each client:
https://phasoric.com/api/mcp
The developer documentation hostname is not the MCP endpoint. OAuth signs you into Phasoric; do not enter Dropbox, Google Drive, or GitHub credentials in your agent's MCP configuration. Phasoric manages those provider connections separately.
Review the Phasoric consent screen. If offered, leave Keep this app connected selected to allow silent renewal. Access tokens last one hour; when continued access is granted, each successful refresh rotates the refresh token and starts a new 30-day renewal window. A client must actually use refresh for this to preserve the connection. Availability of the consent option depends on the deployed release and client capabilities; these setup instructions do not establish overnight reliability for every client.
3. Verify a first read
Open a fresh conversation with the Phasoric tools enabled:
Use Phasoric to list the vaults I can access. Do not change anything.
Then use one returned vault:
Search that vault for my project plan. Read the matching note and summarize
the decisions and their rationale. Include the source note path.
The client should call list_vaults, then pass the returned opaque mappingId into search_notes or get_note_content. Never guess an identifier. A successful connection with no vaults usually needs a mapping or account check, not a new OAuth client.
4. Preview a write
Propose a decision note with the outcome, rationale, source references,
and unresolved follow-ups. Show the destination and exact content.
Do not apply it until I approve.
Supported write tools default to a preview. Application requires human approval, dryRun=false, an idempotency key, mapping permission, and the current content hash when updating an existing note. An agent's ability to read does not prove it can write. See the MCP write contract.
Troubleshooting and disconnecting
| Symptom | Next step |
|---|---|
| No custom connector option | Check the client's plan, version, and organization policy using its linked official guide. |
| Authorization succeeds but no vault appears | Confirm the Phasoric account, active provider connection, and explicit vault mapping. |
| Read works; write is denied | Inspect that mapping's write permission and provider capability. Keep the read connection. |
| Phasoric repeatedly requests sign-in | Reconnect once and approve continued access if offered. Confirm the client supports refresh; do not extend access tokens or copy tokens into prompts. |
| Dropbox/Drive/GitHub needs reconnection | Repair that provider in Phasoric. It is independent of the agent's Phasoric authorization. |
| Tools are missing after an update | Refresh the client's tool list or start a new conversation. |
To revoke OAuth access, open Phasoric Settings → AI Connections & API → Connected applications, then disconnect the application. Removing a client configuration is not a substitute for revoking its Phasoric grant. Manual access tokens are separate credentials and must be revoked separately.
Client instructions were checked against vendor documentation in September 2026. Phasoric's authenticated Vault read was verified in Codex; these guides describe the other clients' documented setup paths, not completed Phasoric interoperability tests on every client.