Vault is a persistent, portable knowledge store you edit like notes and your AI assistants read and update like memory. Claude, ChatGPT and its Dots, Muse, Cursor and Codex see the same notes you do, cite them, and write back.
Waitlist only while we finish billing and multi-user. Markdown in, Markdown out. Your data stays yours.
Danish oil, now that it's moving out to the porch.[1]
Danish oil, reapplied about once a year.[2]
Markdown and attachments in a vault you own. Import an Obsidian vault or start empty.
Vault indexes everything for full-text and semantic search today. Version history is planned.
Connect Claude, ChatGPT and its Dots, Muse, Cursor and Codex over MCP. Each client gets its own permissions and an audit trail, both planned.
The web app is live today. Obsidian sync and desktop and mobile apps are next.
Clients discover the tools over MCP after you approve the connection once. Most tools take an optional vault argument, so one connection reaches every vault in your account. Import a zip to seed a vault, or export one to back it up, both as a background job you can poll from any client. Attachments list, download, upload and delete the same way, gated by plan.
list_directory
Browse one folder: the subfolders and notes directly inside it.
read_note
Read a note: raw is the full file text, content is the body (or one heading's section when heading is given), plus frontmatter, headings, links and a url.
write_note
Create or overwrite a Markdown note at a path.
append_note
Add text to the end of a note, or of one heading's section, without resending the note.
edit_note
Replace an exact passage in a note without resending the note.
move_note
Rename or move a note to a new path and learn which notes still link to the old path so you can update them.
delete_note
Delete a note by path (old versions are kept for 30 days; there is no restore tool yet).
get_index_status
Tell whether a note's latest saved version is searchable yet.
complete_task
Tick (or with done: false, untick) one checkbox task by note path and the line list_tasks reported.
list_notes
List notes across the vault to orient or inventory: recursive by default, filterable by folder and tag (nested tags included), sortable by path, modified time or title, paged with an opaque cursor, with totals and a url per note.
list_tasks
Find checkbox tasks across the vault (open by default, or done, or all), filterable by folder and tag, ordered by note then line, with heading and url.
list_tags
See every tag in the vault with how many notes carry it, most used first; pass a tag to list_notes to open them.
search_text
Find notes by keyword, or by exact phrase when the query is wrapped in double quotes, with an excerpt, score and url per hit.
semantic_search
Find passages by meaning when you don't know the exact words.
get_backlinks
See which notes link to a given note.
get_outgoing_links
See where a note links to, split into resolved paths and unresolved targets.
get_related_notes
Discover notes related to a given one by shared links, shared tags and semantic similarity, ranked with reasons.
get_usage
See how much of this month's agent allowance is left and when it resets: plan, agent operations and semantic searches used against their limits, and the per-minute rate limit.
list_clients
See which AI clients and apps currently hold a sign-in to this vault: name, scope, sessions, first and last seen.
list_vaults
List the vaults on this account, with the default one flagged.
create_vault
Create a new vault on this account; the first one becomes the default.
import_begin
Start a zip import by getting a link to upload an Obsidian-vault zip to.
import_commit
Finish a zip import once the upload succeeds, to unpack it in the background.
export_begin
Start a zip export of the whole vault in the background.
get_job_status
Check an import or export job's status and counts, with a download link once an export is done.
list_jobs
List your recent import and export jobs, newest first.
list_attachments
List attachments (non-note files) across the vault, filterable by folder, each with its size, modified time and a download url.
get_attachment_url
Get a 15-minute download link for an attachment, resolved by path or by a bare filename the way Obsidian resolves an embed.
read_attachment
Read a small attachment inline, up to 4 MB: an image block for images, base64 for everything else.
begin_attachment_upload
Start uploading an attachment too large to send inline: a presigned link to upload directly, bound to the file's size and type.
write_attachment
Create or overwrite a small attachment, up to 4 MB, from base64.
delete_attachment
Delete an attachment by path.
Every edit, whether from the web app or from any connected AI client, publishes one note.changed event (created, updated, deleted) to subscribers. Filter by path_prefix or tag. Deliveries are signed with Standard Webhooks and verified against your callback before the first event is sent.
Vault implements OpenAI's MCP events contract, so a ChatGPT connector or Dot can react to a note the moment it is saved. Read the events docs.
Numbers are the plan at launch and may move before billing opens; waitlist members get the launch annual price.
Bring a standard vault as it is: folders, frontmatter, wikilinks, tags and attachments.
Today, the hosted copy is served over MCP, so Obsidian can still open it. Next, a sync plugin makes Obsidian one more client, not the only one.
Plain Markdown and files, free on every plan, Free included.
Add the server, sign in with your email when the client opens the consent screen, and you're connected.
Settings → Connectors → Add custom connector. Paste the URL.
https://vault.martzmakes.com/mcp
Settings → Connectors → Add connector. Paste the URL and approve the magic-link email.
https://vault.martzmakes.com/mcp
Add Vault as a ChatGPT connector once. A Dot you message or call uses the same connection, with the same notes.
https://vault.martzmakes.com/mcp
Ask Muse to create a custom connector for this MCP server (remote, streamable HTTP) and approve the sign-in email when it connects.
https://vault.martzmakes.com/mcp
Run once in any terminal. Claude Code opens the consent screen.
claude mcp add --transport http vault https://vault.martzmakes.com/mcp
Add to the mcp_servers block of ~/.config/muse/settings.json, then run muse mcp login vault for the consent screen.
"vault": { "transport": "streamable_http", "url": "https://vault.martzmakes.com/mcp" }
Vault is hosted, and every user's data is fenced off at the infrastructure layer. There is no shared database and no server waiting around.
// scoped per session "Resource": "arn:aws:s3:::BUCKET/ tenants/${aws:PrincipalTag/TenantID}/*"
Each user's notes and vectors live under their own prefix. Every request runs with credentials scoped to that prefix, so isolation is enforced by IAM, not only by application code.
Lambda, S3, S3 Vectors, and Bedrock. No vector database server and no always-on infrastructure. When you aren't using it, nothing is running.
You sign in with a one-time email link. AI clients get scoped OAuth tokens you can revoke at any time.
We'll email you when billing opens. One message, no spam.