phygital-brain
OfficialThis server exposes Phygital Brain's skill resources and job launcher — it starts setup/upgrade/team, brain-keeper, or language jobs and lets an agent browse and read the skill's own files (no access to your notes).
Start a Phygital Brain job (
phygital_brain_start): launch asetupjob (default — also handles upgrades and teams), abrain-keeperjob, or anadd-languagejob, and get that job's instructions.Trigger via natural language: responds to phrases like "set up my second brain", "upgrade my second brain", "set up my team", "set up my brain keeper", "translate Phygital Brain into my language", or "switch my brain to another language" (in any language).
Read a single skill file (
phygital_brain_read_file): fetch a form, template, language file, or skill by path relative to the skills folder (e.g.brain-setup/forms/form-1-about-you.html,brain-setup/i18n/ja/templates/root-CLAUDE.md).List skill files (
phygital_brain_list_files): browse the skills folder or any subfolder (e.g.brain-setup/templates,brain-setup/i18n); an empty path lists the top level.Scope limits: read-only and confined to the skills folder — it cannot write, move, or delete files, and it does not touch the user's brain notes in their cloud drive.
Integrates with Dropbox as a cloud drive for the brain's Markdown notes, allowing the agent to read, write, and organize notes in a Dropbox folder.
Connects to Gmail in read-only mode so the Brain Keeper can include yesterday's emails with contacts in daily notes and provide context.
Connects to Google Calendar in read-only mode so the Brain Keeper can note upcoming events and context in daily notes.
Integrates with Google Drive as a cloud drive for the brain's Markdown notes, enabling the agent to read, write, and tidy notes in a Google Drive folder.
Integrates with Nextcloud as a cloud drive and read-only app source, allowing the brain's notes to be stored and accessed, and enabling the Brain Keeper to read emails and calendar data from Nextcloud.
What it is
Phygital Brain is an OS (operating system) for your notes and your AI agent. It builds one folder in your cloud drive (Google Drive, Nextcloud, Dropbox or any drive your agent can connect to), with three kinds of things inside:
Rules: a
CLAUDE.mdfile in every folder. It tells your agent where each kind of information goes, how each note starts, and what to ask you before it changes anything.Notes: plain Markdown files (simple text files with light formatting) about you, your projects, your people, your decisions and your days. Your agent writes them as you talk, and links them together.
The Brain Keeper: a scheduled task that tidies the brain every work day, plus a full check-up whenever you ask for one.
Every chat on that folder starts with your agent reading the rules and the latest notes. So it already knows your name, your clients, your goals and what you did yesterday. You can read and browse the same notes in Baalda, or from your phone through your drive.
It comes as two skills (sets of instructions your agent follows): one builds the brain, one keeps it tidy. They're packaged as a Claude plugin, because Claude is what we use and recommend, but any agent that can work in a folder can follow them. See Other agents.
Related MCP server: big-brain
Yours to keep
You own it. Your brain is a folder of plain text files in your own cloud drive. There's no account with us and nothing to export.
Take it to any AI. Switch to another agent and open the same folder. The new one reads the same notes.
It remembers you. What you tell your agent is saved as notes, so the next chat, or the next AI, starts where you left off.
Free and open source. Anyone can check how it works. Your notes stay private, in your drive: Phygital Brain collects nothing, and your notes go only to the AI you choose.
Why it exists
A chat with an AI ends, and what you told it goes with it. Next time you explain your business, your clients and your project again. The notes you do keep sit in five apps, and none of them talk to your agent.
Phygital Brain gives the agent one place to read from and write to, with rules it follows every time:
Without it | With Phygital Brain |
You explain who you are in every new chat | Your agent reads |
Call notes sit in a chat you'll never find again | The call goes in the project, the client's note and today's daily note, linked |
You forget why you made a decision |
|
Notes pile up and go stale | The Brain Keeper closes old notes, flags stale projects and lists what needs you |
Your agent changes files without asking | It asks before it creates, moves, renames or deletes anything |
How it works
The parts of a computer's operating system each have a match in your brain:
In a computer | In Phygital Brain |
The user | You, talking in plain words |
The processor that does the work | Your AI agent |
The system rules |
|
The file system | Seven folders of Markdown notes in your cloud drive |
Settings |
|
A background service | The Brain Keeper, running every work day |
Apps | Skills: the morning brief, the check-up, and any skill you add |
This is what happens when you tell your agent something:
sequenceDiagram
actor You
participant A as Your agent
participant R as Rules (CLAUDE.md)
participant N as Notes
You->>A: "Had a call with Marta. The cover is due on the 15th."
A->>R: Where does each part go?
R-->>A: Date to the project, call to today, contact to the client
A->>N: Search first, so nothing is made twice
A->>N: Update Projects/Picture-Book, Relationships/Clients/Penguin Kids
A->>N: One line in Daily/2026-10-20, linked to both
A-->>You: "Saved the new date in Picture-Book and the call in today's note."Small updates to notes that already exist happen right away, and your agent tells you in one line. New notes, moves, renames and deletes always wait for your yes. More in How it works.
What you get
A brain built from your answers. People who sell get pages for their business, services and customers. People who don't sell get none of those. A morning brief appears only if you ask for one.
Questions written for your work. The second form starts with three questions your agent writes for your job. An illustrator gets asked about publishers and how they charge; a developer gets asked about their projects and tools.
Projects, people and days, linked. Every person, company and project is a
[[link]], so one click in Baalda takes you from a project to the client to the day you talked.Decisions with the reason. Each decision note says what you chose, why, what you gave up, and the risk. Open decisions show up in your daily note until you close them.
The Brain Keeper. Every work day it makes tomorrow's note, closes old ones, lists open decisions, fixes up to 5 small things and writes a report. A full check-up runs whenever you say "check up my brain".
A morning brief, if you want one: your three most important things, what you're waiting on, and one decision to make.
Meeting prep. Say "prep me for Marta" and get a short brief from your notes: when you last talked, what's going on, what was agreed, what to bring up.
Thinking tools. "Challenge my idea" weighs it against your own notes. "What patterns do you see?" finds what keeps coming up. "Find contradictions" finds notes that disagree.
Your apps, read only. Connect Gmail and Google Calendar (or Outlook, Nextcloud and others) and the Brain Keeper notes yesterday's emails with your people and tomorrow's meetings. It never sends or changes anything.
Fully online, if you want. The Brain Keeper can run as a cloud routine, reading and writing your notes through your cloud drive, with your computer off.
Backups and undo. Before a big change, your agent copies the files into a hidden
.backups/folder for 10 days. "Undo the last change" puts them back.Old notes, any time. "Bring in my old notes" imports from Notion, Google Docs, Apple Notes and others, with a plan you approve first.
Teams. Share one brain through Baalda's cloud, with a Team section in the rules for each person's role.
Your phone. Ask your brain things from your agent's phone app through your cloud drive, or send tasks to your computer (in Claude, with Dispatch).
Your language. The forms, messages and notes are in the language you pick. File and folder names stay in English, so the rules work the same everywhere.
Writing that sounds like you. Every brain comes with the no-ai-slop skill. Your agent writes in your voice, then checks for AI-sounding patterns before anyone else reads it.
Careful work habits. The main rules include Andrej Karpathy's guidelines for AI assistants: ask when unsure, pick the simplest way, change only what's needed, check the work.
Your own rules. When you correct your agent, it saves the correction as a new rule, in your words. Upgrades never change those rules.
How your agent works
The work habits are Andrej Karpathy's guidelines for AI assistants (andrej-karpathy-skills), built into every brain's main rules in our own words. The Writing Check uses the no-ai-slop skill, which every brain gets in Skills/no-ai-slop/. More in Main rules.
Inside your brain
My Brain/
├── CLAUDE.md the main rules
├── .claudeignore what your agent never reads unless you ask
├── About/ me.md, goals.md, business.md, services.md, brand.md ...
├── Daily/ 2026-10-20.md, 2026-10-21.md ... and tasks.md
├── Projects/ Picture-Book/README.md, Portfolio-Website/README.md ...
├── Relationships/ Clients/, Collaborators/, Team/, Partners/
├── Memory/ decisions/, research/, finances/ (private), archive/
├── Library/ prompts, templates, checklists
└── Skills/ brain-keeper/, morning-brief/Each folder has its own guide: what goes in it, what you can say, examples and its rules. Start at The folders in your brain.
Quick start
You need an AI agent that can work in a folder, a cloud drive your agent can connect to, and a computer. No code. We recommend Claude with Google Drive, the pair we tested most, so the steps below use them. The full steps, with other drives and agents, are in Getting started.
Step | What you do | Time |
1 | Get your agent: we recommend the Claude desktop app with a paid plan | 3 min |
2 | Install your cloud drive's desktop app (for example Google Drive), and make a folder for your brain inside it | 3 min |
3 | In your agent, start a task and choose that folder | 1 min |
4 | Connect the drive to your agent (in Claude: Settings, Connectors), so your phone can reach the brain | 1 min |
5 | Download Baalda and open the same folder | 2 min |
6 | Install Phygital Brain (one click, below) and say "Set up my second brain." | 10 min |
Install: click the button for your agent.
Or in a terminal, for any agent that uses skills (Claude Code, Codex, Cursor, Gemini CLI and others):
npx skills add Phygital-Brain/phygital-brainIt asks which of your agents to add it to. Claude desktop and Claude Code need nothing more. The other ways need Node.js, a free one-time install.
Every way, step by step: Install.
flowchart LR
C[Checks: the folder] --> L[Language] --> W[Welcome]
W --> CD[Cloud drive:<br>connect and check] --> F1[Form 1<br>About you] --> F2[Form 2<br>Your work] --> F3[Form 3<br>Days and people] --> F4[Form 4<br>Files]
F4 --> B[Build: folders, rules,<br>notes, Brain Keeper]
B --> D[One short message:<br>what was built, how to use it]At the end, your agent welcomes you as your personal assistant, and offers Baalda to browse your notes like an app.
A week with your brain
Ana is an illustrator in Lisbon. She sells picture-book work to publishers and set up her brain on Monday.
Monday, 10:00. She answers the four forms and drops in her CV and price list. Her agent builds
About/me.md,goals.md,services.md, three projects and a note for her editor's publisher.Tuesday, 08:00. Her morning brief lists three things: send the sketches, reply to a bakery about a logo, and decide on her cover price.
Tuesday, 15:00. After a call she says: "Marta wants the cover by the 15th." The project, the client note and the day are updated and linked.
Wednesday, on the bus. In her agent's phone app she asks: "What did Marta and I agree on Tuesday?" It finds the note in her drive.
Thursday. "I decided to raise my cover price to 400 from January." Her agent asks a little about why, then writes
Memory/decisions/2026-10-23-raise-cover-price.md.Every work day, 07:00. The Brain Keeper makes the next day's note, closes old ones and fixes small things. Each morning it lists the cover-price decision as still open, until she closes it.
More people, from a bakery owner to a student, are in Use cases.
On your phone
Way | What it does | Your computer |
Ask: your agent's phone app, with your drive connected | Finds and reads what's in your brain | Can be off |
Do: sending a task to your agent on your computer (in Claude, Dispatch) | Adds and files things with all the rules | Must be on, with your agent's app open |
Setup, what to say, and fixes for common problems: Your brain on your phone.
Languages
Phygital Brain is ready in 41 languages. Pick yours at the start of the setup, and the whole brain is built in it: the forms, the rules, the folder and note names, the Brain Keeper and every message.
See the full list of languages.
Your language isn't here? Pick Other and type it. Your agent translates the whole brain during the setup, folder names included, without asking you anything. To make a checked set that everyone who speaks your language can use, say:
Translate Phygital Brain into my language.
The add-language skill asks you three things (formal or informal "you", the main folder names, and the names for the Brain Keeper and the morning brief), translates everything, checks it, and shows you how to use it and share it. How it works, step by step: Languages.
Switching later: say "Switch my brain to Spanish". Your agent renames the folders and swaps the rules, with a backup first and your yes.
Works with your agent
Claude desktop app | Agents that work in a folder (Claude Code, Codex, Hermes Agent, OpenClaw) | Chat apps that can't save files | |
Build the brain | Yes | Yes | No |
The four form windows | Yes | The same questions, in chat | No |
Daily use | Yes | Yes | Read only |
Brain Keeper and morning brief | Yes, scheduled | If the app can schedule tasks | No |
The rule files are called CLAUDE.md. Agents that look for another name, like AGENTS.md in Codex, get a one-line file that points to CLAUDE.md, so there's only one set of rules. More in Other agents.
Privacy
Your notes are read by your AI agent and stored in your cloud drive. Phygital Brain itself has no server and collects nothing. More in What you share with your AI.
Private details stay in one place. Tax IDs, bank details, card numbers, your full legal name and your birth date live only in the note that needs them. Your agent never copies them into other notes, and never repeats them in a reply.
A "never read" list.
.claudeignorecovers password and key files andMemory/finances/. Your agent opens those only when you ask for an exact file. Your agent follows this as a rule, but nothing is locked.No secrets in notes. Passwords, keys and tokens belong in a password manager.
What it isn't
The full list is in Limits.
No app. There's nothing to run. Your AI agent does the work, following the files in this repository.
No lock yet. The rules work only because your agent follows them. Keep truly secret things outside the brain folder. Locked folders are on the roadmap.
Not always on, unless you move it to the cloud. On your computer, the Brain Keeper and the morning brief run only while your agent's app is open. As a cloud routine, they run with the computer off.
An early version. This is version 0.1.9, and the setup hasn't been tested with many people yet.
Roadmap
Planned, not built yet:
Locked folders. You choose which folders to lock, like
Memory/finances/. Their notes are encrypted in your drive, so no app or agent can read them without you. You unlock them with your password or fingerprint, from the agent you already use, and only for what you approve.
Ideas are welcome: open an issue on GitHub.
Updating and leaving
To update: update the plugin (in Claude Code, /plugin marketplace update phygital-brain), then say "Upgrade my second brain." Your agent shows what's new and asks first. Your notes and your own rules stay as they are.
To change your answers: say "Update my answers." The forms open again, and your About pages are refreshed.
To leave: uninstall the plugin. Your brain is a folder of plain text files in your own cloud drive. Any app that reads Markdown can open it.
FAQ
The most asked questions are below. The full list, with 92 answers grouped by topic, is in the FAQ.
No. You install a few apps, answer four forms and talk in plain words. The only lines that look like code are the two install lines for Claude Code, and you can paste them.
Any agent that can read, edit and create files in a folder on your computer. Claude is what we use and recommend: it's the only one that shows the setup as form windows, and it can schedule the Brain Keeper. Codex, Hermes Agent, OpenClaw and similar agents ask the same questions in chat. See Other agents.
Any drive that keeps a copy of the folder on your computer and that your agent can connect to, so it can read, edit and create files there: Google Drive, Nextcloud, Dropbox, OneDrive and others. Claude has a built-in Google Drive connector; other drives usually connect through an MCP server. See Cloud drives.
It saves small updates to notes that already exist and tells you in one line. It asks before it makes a new note, rewrites one, or moves, renames or deletes anything. The Brain Keeper never deletes your notes.
Phygital Brain is free and open source. You pay for your AI agent and, if you need more than the free space, your cloud drive.
All the guides
Guide | What's in it |
Five people, what their brain looks like, and what they say on a normal day | |
92 questions and answers, grouped by topic | |
One click for Claude desktop, Cursor and VS Code, and steps for Claude Code, Codex, Hermes Agent, OpenClaw and others | |
Every step from nothing to a working brain, with checks and fixes | |
Gmail, Calendar, Drive and other services, read only, and running fully online | |
Adding any skill to your brain, making videos with HyperFrames and editing images with PhotoCraft | |
Sharing one brain through Baalda's cloud | |
Exporting from Notion, Google Docs, Apple Notes and others, and filing it all | |
A few made-up notes, so you can see the files before you build yours | |
What your agent does at each step, when it saves and when it asks | |
One page per folder and subfolder, with examples and rules | |
The main | |
Ask from your agent's phone app, send tasks to your computer | |
Using Codex, Hermes Agent, OpenClaw or another agent, rule file names, two agents on one brain | |
How other languages work | |
What it does badly, or not yet | |
Every term, in plain words | |
What you share with your AI, and how to report a problem |
This repository
Folder | What |
| The setup: the agent's instructions, the four forms, and every file a new brain gets |
| The Brain Keeper: the daily tidy and the check-up |
| Making a full set in a new language, or switching a brain's language |
| The built language sets the setup copies |
| The guides above, and the images |
| The translations (one file and folder per language) and how to add one |
| The checks to run before a change ( |
| The plugin files, for installing it in Claude |
| The connector (an MCP server, no dependencies) for agents that take MCP servers |
| The npm package, so |
| Releases each new version: npm, and the GitHub release with the Claude desktop file |
Help and contributing
Questions, bugs and ideas: open an issue on GitHub. To change something, read CONTRIBUTING.md and AGENTS.md. Report security or privacy problems privately, as SECURITY.md explains. To cite the project, use CITATION.cff.
Open source and credit
Free and open source under the Apache License 2.0. Keep the NOTICE file: it carries the line "Created by Phygital-Brain".
The licence doesn't cover the name and logo (see TRADEMARKS.md). You can say your work is "built on Phygital Brain", but you can't sell it under that name.
No warranty
Phygital Brain is provided as is, without warranty of any kind (see sections 7 and 8 of the licence). You're responsible for what you put in your brain and what you share with your AI provider.
Available Tools
3 toolsphygital_brain_list_filesList Phygital Brain filesARead-onlyIdempotent
List what's in one of Phygital Brain's folders: one name per line, sorted, with folders ending in '/'. It doesn't look inside subfolders: list a subfolder to see its files. Use it to find a file's exact name, then open the file with phygital_brain_read_file. A folder that doesn't exist returns an error. It reads only Phygital Brain's files, never the person's brain, and changes nothing.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | The folder inside Phygital Brain's skills folder, like 'brain-setup/templates' or 'brain-setup/i18n'. Leave empty to list the skills. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, yet the description still adds behavior the annotations cannot express: no recursion into subfolders, an error for nonexistent folders, and the scope boundary that it reads only Phygital Brain files, never the person's brain. 'Changes nothing' mildly restates the annotations, but the recursion and error semantics are genuine additions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core behavior and output format, then usage routing, then edge cases. Four short sentences, none of which is filler; the caveats (no recursion, error on missing folder) are the ones an agent actually needs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, so the description carries the return-format burden and does so precisely (one name per line, sorted, trailing '/' for folders). Combined with the recursion, error, and scope notes, an agent has everything needed to call this correctly on the first try.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single optional 'path' parameter is already fully documented in the schema, including the empty-value default. The description only implies that path names a folder rather than a file, adding little beyond what the schema supplies; baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb (List) plus resource (files in a Phygital Brain folder), and it goes further by describing the exact output shape: one name per line, sorted, folders suffixed with '/'. It separates itself from the sibling phygital_brain_read_file by naming that tool as the follow-up step for reading file contents.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states the use case ('Use it to find a file's exact name, then open the file with phygital_brain_read_file') and routes the agent to the correct alternative for the adjacent task. It also states the non-recursive behavior and the remedy ('list a subfolder to see its files'), so the agent knows what to do instead of expecting recursion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
phygital_brain_read_fileRead a Phygital Brain fileARead-onlyIdempotent
Read one of Phygital Brain's own files and return its full text: a form, a template, a language file or a skill. Use it when the instructions from phygital_brain_start name a file; if you don't know the exact name, list the folder with phygital_brain_list_files first. A missing file, a folder, or a path outside the skills folder returns an error that says so. It reads only Phygital Brain's files, never the person's brain, and changes nothing.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | The file's path inside Phygital Brain's skills folder, like 'brain-setup/forms/form-1-about-you.html' or 'brain-setup/i18n/ja/templates/root-CLAUDE.md'. Paths that start with a brain folder (About/, Daily/, Projects/...) are in the person's brain, not here. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new behavior: the error cases (missing file, folder, path outside skills folder return an error that says so) and the strict read scope ('never the person's brain, and changes nothing'). It stops short of describing pagination or size limits, but for a single-file read that is minor.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loads what is returned, then usage, then failure modes and scope in four tight sentences. Each sentence contributes, though the brain-file exclusion is asserted in both the description and the schema example, a mild redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, and the description supplies the return value ('return its full text'), the error behavior, and the scoping boundary. For a one-parameter read tool with full annotation coverage, nothing an agent needs to invoke it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the property description already explains the skills-folder path and the brain-folder exclusion with examples, so the description's path scoping largely restates structured data. Baseline 3 is appropriate since the schema does the heavy lifting for the single parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names a specific verb (read) and resource (one of Phygital Brain's own files), enumerates what kinds of files it covers (form, template, language file, skill), and explicitly contrasts itself with phygital_brain_list_files and the person's brain. An agent can distinguish it from its siblings without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit trigger ('use it when the instructions from phygital_brain_start name a file') plus a fallback routing rule ('if you don't know the exact name, list the folder with phygital_brain_list_files first'). Both the when and the alternative are stated, not implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
phygital_brain_startStart a Phygital Brain jobARead-onlyIdempotent
Start a Phygital Brain job: returns that job's step-by-step instructions (a skill) as text, for you to follow. It changes nothing by itself: you then build or change the person's brain with your own file tools, in the folder they chose. Call it first when the person says 'set up my second brain', 'upgrade my second brain', 'set up my team', 'set up my brain keeper', 'translate Phygital Brain into my language', 'switch my brain to another language', or the same in another language. Calling it again returns the same instructions. To open a file the instructions name, use phygital_brain_read_file; to see which files exist, use phygital_brain_list_files. An unknown job returns an error naming the valid ones.
| Name | Required | Description | Default |
|---|---|---|---|
| job | No | Which job: 'setup' (the default; also upgrades a brain and sets up a team), 'brain-keeper' (set up, update or move the scheduled task that tidies the brain) or 'add-language' (make Phygital Brain in a new language, or switch a brain's language). |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds real context beyond the annotations: the tool mutates nothing itself (the agent must apply changes with its own file tools), repeat calls yield identical instructions, and an unknown job returns an error listing valid ones. Idempotency is partly restated from the annotation, but the error behavior and the 'you do the writes' division of labor are genuinely new information.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The key fact (what you get back and that it changes nothing) is front-loaded, and each subsequent sentence carries distinct routing or error information. The trigger-phrase list is long, but it is functional rather than filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, and the description compensates by describing the return value (a text skill to follow), the error case, and the follow-up tool calls. For a single-parameter, zero-required tool this leaves nothing an agent needs missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the enum values are already fully described in the schema, so the baseline is 3. The description does add a little mapping value by tying natural-language triggers to job values (e.g. 'set up my team' implies 'setup'), but it adds no new syntax or constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Start a Phygital Brain job') and immediately clarifies the actual return: step-by-step instructions as text. It also distinguishes itself from the two siblings by naming them and their roles, so an agent can tell the three apart without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says to call it first and enumerates concrete user phrasings that should trigger it ('set up my second brain', 'switch my brain to another language', etc.). It also routes follow-up needs to the right siblings: phygital_brain_read_file for opening named files, phygital_brain_list_files for discovery.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
v0.1.9- Changed
phygital_brain_list_files1 field changed- changed
Input schema / properties / path / descriptionPrevious value: -"Folder inside the skills folder. Default: the top."New value: +"The folder inside Phygital Brain's skills folder, like 'brain-setup/templates' or 'brain-setup/i18n'. Leave empty to list the skills."
- Changed
phygital_brain_read_file1 field changed- changed
Input schema / properties / path / descriptionPrevious value: -"Path inside the skills folder."New value: +"The file's path inside Phygital Brain's skills folder, like 'brain-setup/forms/form-1-about-you.html' or 'brain-setup/i18n/ja/templates/root-CLAUDE.md'. Paths that start with a brain folder (About/, Daily/, Projects/...) are in the person's brain, not here."
- Changed
phygital_brain_start1 field changed- changed
Input schema / properties / job / descriptionPrevious value: -"Which job. Default: setup."New value: +"Which job: 'setup' (the default; also upgrades a brain and sets up a team), 'brain-keeper' (set up, update or move the scheduled task that tidies the brain) or 'add-language' (make Phygital Brain in a new language, or switch a brain's language)."
3 tool updates
v0.1.8- First observed
phygital_brain_list_files - First observed
phygital_brain_read_file - First observed
phygital_brain_start
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list_files enumerates directory contents, read_file returns a single file's text, and start provides job instructions. There is no overlap in function, and the descriptions make the intended use and dependencies explicit.
All tools share the predictable phygital_brain_ prefix and use snake_case. However, two tools follow a verb_noun pattern (list_files, read_file) while start is a bare verb, a minor deviation from strict consistency.
Three tools are well-matched to the server's narrow purpose of delivering instructions and reading its own files. Each tool is necessary, and the count avoids redundancy while remaining sufficient for the task.
The surface covers the full lifecycle needed for this read-only helper: start a job to get instructions, list relevant files, and read their contents. No critical gaps exist, and the server intentionally avoids write operations, which are delegated to the user's own tools.
Maintenance
Related MCP Connectors
The second brain your AI agents share. It builds itself from your work and keeps itself current.
Markdown notes in folders, with files, that your AI assistant can read, write and organise.
Markdown notes in folders, with files, that your AI assistant can read, write and organise.
A second brain for Claude: remembers your work, plans your day, encrypted under a key only you hold.
Related MCP Servers
- AlicenseBqualityFmaintenanceProvides an agent-first note-taking system designed from the ground up for AI collaboration. Organizes your notes as a local vault of ordinary markdown files with semantic note types.28131 npm10MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to read and write to a personal knowledge vault of markdown notes, projects, and tasks, with tooling for search, capture, daily logs, and project management across different AI tools.231MIT
- AlicenseNot gradedqualityAmaintenanceA personal, offline-first memory for AI assistants that enables them to read, search, and write to a shared folder of Markdown files, so they all remember you without needing a cloud.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to capture, structure, remember, and retrieve source-backed memory as local Markdown files, with reviewable writes and no cloud dependency.213MIT