Skip to main content
Glama

Server Details

Pick up where you left off: your project's progress, decisions and notes, kept in your own storage.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.5/5.0

Scored across 16 tools

Disambiguation3/5

Most tools target distinct resources or operations, but capture_correction overlaps meaningfully with supersede: capture_correction appends a correction and says the old entry is marked superseded, while supersede separately marks any record entry as superseded. The four capture_* tools are otherwise differentiated by their target list, and read_file/read_home/raw_source remain readable as distinct despite some conceptual closeness.

Naming Consistency4/5

Most names follow a readable verb_noun pattern: capture_*, connect_storage, list_homes, read_file, read_home, save_note, setup_home, update_home_file. Minor deviations exist in raw_source (noun phrase), supersede (bare verb), and organize_prepare/organize_save (category-style prefix), so the convention is mostly but not fully consistent.

Tool Count4/5

Sixteen tools is slightly above the typical 3-15 well-scoped range but remains reasonable for a rich home/project memory system with storage connection, setup, capture variants, organizing, and file updating. Each tool appears to earn its place, though the set is close to feeling heavy.

Completeness4/5

The surface covers setup, storage connection, home reading, note saving, raw-source preservation, append-only record capture, superseding, organizing, and home-file updates, so core workflows have endpoints. Minor gaps remain, such as no explicit detach-storage tool or standalone listing of record entries, though read_home returns inventory and append-only constraints are intentional.

Publisher details

Operator
Living Projects · Publisher source
Vendor relationship
First-party · Publisher source
Privacy policy
Not provided
Trust center
Not available
Restrictions
A Dropbox, Google Drive or OneDrive account. Works with Claude, ChatGPT and Gemini. On Gemini, a Google AI Pro or Ultra plan is needed. · Publisher source

Available Tools

16 tools
capture_correctionRecord a correctionAInspect

Living Projects — Append one entry to this home's CORRECTIONS list: one saved fact replaced by another. The old entry stays and is marked superseded. Doubt wording and telling words outside quoted words — "remains to be confirmed", "unconfirmed", "should", "never" and the like — are saved as written, and the answer marks the lines. All four fields are required; the write is verified before VERIFIED is returned. Append-only — there is no edit and no delete. An entry is the short form of what was settled: one or two sentences per field, about 80 words in all. The detail of a sitting lives in its dated note; a field with detail there ends with a pointer to it.

Inputs: home_path (required), why_it_was_wrong (required), what_was_saved_and_where (required), what_else_was_updated_to_match (required), +1 more.

capture_decisionRecord a decisionAInspect

Living Projects — Append one entry to this home's DECISIONS list: something was chosen, and why. Doubt wording and telling words outside quoted words — "remains to be confirmed", "unconfirmed", "should", "never" and the like — are saved as written, and the answer marks the lines. All four fields are required; the write is verified before VERIFIED is returned. Append-only — there is no edit and no delete. An entry is the short form of what was settled: one or two sentences per field, about 80 words in all. The detail of a sitting lives in its dated note; a field with detail there ends with a pointer to it.

Inputs: why (required), home_path (required), what_it_replaced (required), what_was_decided (required), +1 more.

capture_definitionRecord a definitionAInspect

Living Projects — Append one entry to this home's DEFINITIONS list: a word the owner uses in a fixed way. Doubt wording and telling words outside quoted words — "remains to be confirmed", "unconfirmed", "should", "never" and the like — are saved as written, and the answer marks the lines. All four fields are required; the write is verified before VERIFIED is returned. Append-only — there is no edit and no delete. An entry is the short form of what was settled: one or two sentences per field, about 80 words in all. The detail of a sitting lives in its dated note; a field with detail there ends with a pointer to it.

Inputs: the_word (required), home_path (required), what_it_usually_means (required), where_it_was_first_said_and_where_its_used (required), +1 more.

capture_rejectionRecord a rejectionAInspect

Living Projects — Append one entry to this home's REJECTIONS list: a path considered or tried and dropped, and why. Doubt wording and telling words outside quoted words — "remains to be confirmed", "unconfirmed", "should", "never" and the like — are saved as written, and the answer marks the lines. All four fields are required; the write is verified before VERIFIED is returned. Append-only — there is no edit and no delete. An entry is the short form of what was settled: one or two sentences per field, about 80 words in all. The detail of a sitting lives in its dated note; a field with detail there ends with a pointer to it.

Inputs: why (required), home_path (required), what_was_dropped (required), what_was_kept_instead (required), +1 more.

connect_storageConnect storageAInspect

Living Projects — Attach another storage (Dropbox, Google Drive, or Microsoft OneDrive) to this connection: returns a one-time link the owner opens to approve on that storage's own page. Afterwards the list of homes spans every attached storage; a home still lives whole in ONE storage. If two storages hold a same-named home, name the storage in the path, e.g. 'dropbox:/condo'.

Inputs: storage (required).

list_homesList project homesA
Read-only
Inspect

Living Projects — List every Living Projects home in the connected storage, by path. Reads names only.

Inputs: no named parameters.

name_platformName this AI's notes folderAInspect

Living Projects — Name the notes folder this platform stages to, where the plugin has no name for the tool that connected. Claude, GPT and Gemini platforms are named by the plugin from the name they give at the door, or from their registration where that name gives none. The answer is kept on this connection, carried across a reconnect, and is the name in every home; once a note is saved under a name, or where the plugin gave the name, pressing this again changes nothing. Notes only — captures do not depend on it. Pressed once after a NOT FOUND answer from save_note; the same save then goes through.

Inputs: shelf (required).

organize_prepareGather a home for organizingB
Read-only
Inspect

Living Projects — Reads the record's full inventory and complete contents, places the staged notes since the last standing whole after them, and names the earlier notes and the parking lot. Read-only: it writes nothing. Runs before organize_save.

Inputs: home_path (required).

organize_saveSave where the work standsB
Destructive
Inspect

Living Projects — Rewrites the home's current standing with the text it is given. Refuses unless organize_prepare ran recently on this connection, and one prepare opens one save. A hand this home is missing is supplied here. Takes the owner's own answer and keeps it in the standing's header. With the answer blank it is the preview: it writes nothing and shows the lines the finder marks, before the owner's yes. It cannot tell whether the owner was actually asked — it checks that an answer is carried, not that it is true. Doubt wording and telling words outside quoted words — "remains to be confirmed", "unconfirmed", "should", "never" and the like — are saved as written, and the answer marks the lines.

Inputs: home_path (required), owner_answer (required), standing_text (required).

raw_sourceSave words exactly as givenCInspect

Living Projects — Keep a long first-person account whole and verbatim as a permanent raw-source artifact.

Inputs: title (required), content (required), home_path (required).

read_fileRead a fileA
Read-only
Inspect

Living Projects — Read one file inside a home (path relative to the home). Read-only; paths outside the home are refused. An address that begins with the home's own name is read from inside the home.

Inputs: home_path (required), relative_path (required).

read_homeRead a project homeA
Read-only
Inspect

Living Projects — A home's home file, current standing, record inventory and staged notes, returned together — where the work in this home stands. Where the home file is out of date it answers with the update offer ALONE and waits for the owner's yes or no; read the home again after either and it shows whole. The question comes at every read until it is answered; the answer is given through update_home_file. Read-only: it writes nothing. A hand this home is missing is named, and the next organize_save supplies it.

Inputs: home_path (required).

save_noteSave a noteAInspect

Living Projects — Save a dated, create-only note into this platform's own notes folder inside the home. The notes folder is named by the plugin from the name this tool gave at the door, and it is the same name in every home; a notes folder renamed by hand inside the home is still found. There is no argument for naming it: the caller does not name the notes folder. A note holds what settled, in the owner's words. It is saved once the file verifiably exists. An idea with no home yet goes to the home's own Parking Lot folder instead of a notes folder. A note whose name begins fact holds one thing that became true without being chosen — "fact — next keep-alive click before 27 September". The name is the fact, and the newest name on a subject is the current one. A settled fact inside a longer note — a submission, a status change — is also saved as its own fact note, so the facts list shows it by title. A NOT FOUND answer means no folder name is saved on this connection yet: the owner names the folder once, name_platform keeps the answer, and the same save then goes through. Doubt wording and telling words outside quoted words — "remains to be confirmed", "unconfirmed", "should", "never" and the like — are saved as written, and the answer marks the lines. Language: The record is written as a description of what is true, what was settled, and how the work runs. A sentence that describes what happened stays true after the moment passes. Code blocks and quoted words are kept as they are. Example: The cat likes the tree because there are birds in it. It climbs up in the mornings, when the birds are loudest.

Inputs: title (required), content (required), home_path (required), parking_lot.

setup_homeSet up a project homeA
Destructive
Inspect

Living Projects — Install a Living Projects home into a folder in the connected storage (Dropbox, Google Drive, or OneDrive). The folder is made when it is missing, so nothing needs checking or confirming before the press. The home is a Living Projects folder holding an empty record folder, a plugin folder, and the home file (HOME.md) copied from the standard text with the project's name filled in. Notes folders are not pre-built — each platform's is born there when it first saves. The project's folder itself becomes the home: it installs into the folder it is given, beside whatever is already there. An existing home file stops the install; the three script hands are written over where the plugin folder holds them; nothing else in the folder is touched.

Inputs: home_path (required), project_name (required).

supersedeMark an entry as replacedBInspect

Living Projects — Mark a record entry as superseded, with the reason and the kind it is in (decision, rejection, definition, or correction). History stays; there is no button for deleting or editing it.

Inputs: kind (required), reason (required), home_path (required), entry_number (required).

update_home_fileUpdate the home fileA
Destructive
Inspect

Living Projects — Rewrite this home's home file (HOME.md, in its Living Projects folder) from the standard text, keeping the old one beside it as a dated copy. Pressed only on the owner's yes — a home file is the owner's own writing, and anything in it that is not in the standard is lost from the live file (recoverable from the copy kept beside). WITH PREVIEW TRUE IT ANSWERS WHAT IS IN THE UPDATE — what the new version contains, where this home's file stands, what a yes does, what a no does, what would be lost, and the whole new text — AND WRITES NOTHING. WITH DECLINE TRUE IT RECORDS THE OWNER'S NO — writes the marker only, so the question waits for the next standard, and changes nothing else. On a yes it touches the home file and writes the marker.

Inputs: preview (required), home_path (required), decline.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Saves the current state of a project — decisions, rejected approaches, open questions and the actual files — and hands it to any new chat, so you never re-explain a project twice. Local-first: everything is written to your own disk as plain Markdown and JSON, with no account and no telemetry.
      55 npm
      2
      Elastic 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Keeps your notes, decisions and projects in one folder on your own server, so your AI assistant picks up where the last chat ended. Reads and searches PDF, Word, Excel and mail as text; write policies per folder, a trash instead of delete.
      20
      61 npm
      2
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources