- Home
- Skills
- Agents & Orchestration
- brain mcp
Works with the AI Agents you already use
brain mcp
Connect your agent to your Obsidian vault to recall project history, preferences, and past decisions.
Free
brain mcp
Example session with this skill installed
What were my last few decisions regarding the database migration, and based on those, what should I do next for the API refactor?
- Read your context and instructions
- Compiled the brain mcp
I searched your vault for recent activity and decision records related to the database migration.
Migration Context & Next Steps
Based on your notes in Projects/Infrastructure/Decisions/2023-11-Migration.md, we decided to favor
pnpm over npm for package management and to always run a
dry-run migration before touching production. Your recent log in Captures/Session-2023-12-01.md notes that the ledger DB schema is now locked.
| Source Note | Key Decision / Context |
|---|---|
Decisions/2023-11-Migration.md | Use pnpm for all workspace packages to ensure lockfile consistency. |
Decisions/2023-11-Migration.md | Mandatory --dry-run flag for all Prisma migration scripts. |
Captures/Session-2023-12-01.md | Ledger DB migration completed; schema is immutable for Q4. |
Recommended Next Steps for API Refactor:
1.
Update CI/CD: Ensure the refactor PR pipeline uses pnpm recursive install to match the migration's tooling decision.
2.
Schema Validation: Implement a validation layer in the API that strictly follows the locked Ledger DB schema found in your schema.prisma.
3.
Dry-Run Scripting: Create a scripts/refactor-test.sh that mimics the migration's dry-run requirement for the new API endpoints.
Next steps
- Would you like me to
brain_capturethis refactor plan to yourProjects/API/folder? - I can search for your
OAuthnotes if the refactor involves auth changes.
Connects securely to your tools. The creator never sees your data.
About this skill
Working with an agent that lacks context of your personal preferences, past decisions, and project history leads to repetitive explanations and shallow assistance. This skill bridges the gap by connecting your agent to your Obsidian vault via an MCP server, allowing it to treat your notes as its primary source of truth.
What it does
- Load identity - retrieves your specific profile, work preferences, and project goals to tailor every interaction.
- Contextual retrieval queries your vault for specific facts, decisions, or project details using hybrid search.
- Activity tracking summarizes recent work by analyzing note modifications and project progress over specific timeframes.
- Memory persistence saves new preferences, constraints, or durable facts back to your vault with explicit consent.
- Document capture generates meeting notes, research summaries, and project plans directly into your
Captures/folder. - Graph exploration discovers relationships between notes and concepts to find related work or dependencies.
How it works
- Initialize the connection to your
brain-mcpserver to verify the agent can access your Markdown files. - Retrieve context using tools like
brain_identityorbrain_contextto ground the current task in your existing documentation. - Synthesize answers by citing specific note IDs and vault paths so you can verify the sources of the agent's suggestions.
- Update records via
brain_rememberorbrain_captureto ensure new insights or changes are stored for future sessions.
Frameworks & tools
This skill requires the brain-mcp server and an Obsidian vault containing plain Markdown files. It uses hybrid keyword and semantic search to interface with local file structures.
Why this beats prompting it yourself
Manual context injection is limited by token windows and requires you to constantly copy-paste your own notes. This skill automates the retrieval of exactly what is relevant, ensuring the agent "remembers" your feedback and preferences without manual reminders.
Use cases
- Project planning by referencing previous decision records and progress logs to suggest next steps.
- Onboarding agents to your personal coding style and workflow constraints from a central identity note.
- Recalling history to answer questions about why specific architectural choices were made months ago.
- Automated journaling by capturing session logs and durable facts directly into your second brain.
Known limitations
The agent cannot run the initial server installation and requires the vault to be pre-existing. It only has write access to designated Notes/ and Captures/ folders.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
1 people have installed this skill.
Trust & safety
Security scanned
Verified clean 11 days ago
- Free to download with an account
Requires