The Flint Note server provides comprehensive API access for managing notes, note types, vaults, and knowledge graph relationships in a local-first note-taking system.
Note Operations: Create, read, update, rename, and delete notes with markdown content, metadata, and batch processing support. Updates use content hashes for optimistic locking to prevent conflicts.
Note Type Management: Define custom note types with metadata schemas, agent instructions, and validation. List, update, delete, and migrate note types, with options to view all notes belonging to a specific type.
Search & Discovery: Search notes using simple queries, regular expressions, or structured filtering by content, type, metadata, dates, and relationships. Advanced search supports sorting and pagination, while SQL queries provide maximum flexibility (SELECT only).
Link & Graph Analysis: Track wikilinks between notes with backlink retrieval, outgoing/external link analysis, broken link detection, and link-based search. Automatic wikilink updates when renaming notes.
Vault Management: Create, list, switch, update, and remove local data vaults with vault-scoped operations and multi-vault support. Active vault context controls which notes and types are accessible.
Key Features: Local-first storage, flexible metadata schemas, field projection for response control, batch operations, and optimistic locking for data consistency.
Flint is a note-taking app that helps you capture ideas, connect them together, and make them part of how you think.
Status
Flint is currently in beta. Expect some bugs and unfinished polish as development continues. We welcome feedback and contributions!
Related MCP server: OneNote MCP Server
The Deep Knowledge Cycle
Flint aim is to build deep knowledge by supporting the complete learning cycle of externalizing (getting ideas out), internalizing (making them yours), and resurfacing (bringing them back repeatedly over time to ground memory).
Most tools optimize for one part of this cycle. Flint optimizes for the entire process.
1. Externalize
Getting ideas out of your head without barriers. The system handles organization so you can focus on thinking.
2. Internalize
Making ideas yours through connection and reflection. This is where notes become knowledge.
3. Resurface
Active recall brings past ideas back at optimal intervals, grounding them in memory.
Core Principles
Notes as thinking units - Think in ideas and connections, not files and folders
Agent assistance, not replacement - AI helps with structural tasks while you think
Frictionless capture - No barriers to writing things down
Plain text first - Markdown files you own, no proprietary formats
Local-first - Your data stays on your machine
Open source - No vendor lock-in, community-driven development
Read docs/FLINT-OVERVIEW.md for a deeper understanding of Flint's philosophy.
Quick start
Flint is built with Electron, Svelte 5, and TypeScript.
Quick Start
Documentation
Getting Started - Step-by-step setup guide
Flint Overview - Philosophy and core beliefs
Core Concepts - Fundamental concepts
Architecture - System architecture
Design - UI design and components
Contributing
Flint is open source and welcomes contributions! Whether you want to fix bugs, add features, or improve documentation, we'd love your help.
See CONTRIBUTING.md for detailed guidelines.
License
Flint is licensed under the GNU General Public License v3.0.
Community & Support
GitHub - github.com/disnet/flint-note
Website - flintnote.com
Documentation - flintnote.com/docs
Discord - Join the community
Issues - Report bugs and request features on GitHub Issues
Discussions - Ask questions and share ideas on GitHub Discussions