Skip to main content
Glama

Flint Note

by disnet
SETUP.md6.78 kB
# flint-note Setup Guide ## Overview flint-note is an agent-first note-taking application that uses the Model Context Protocol (MCP) to provide AI agents with direct access to your personal knowledge base. This guide will help you set up and start using flint-note. ## Prerequisites - Node.js 18.0.0 or higher - npm or yarn package manager - An MCP-compatible chat client (like Claude Desktop, Cody, or custom MCP clients) ## Installation 1. **Clone or download the project:** ```bash git clone <repository-url> cd flint-note ``` 2. **Install dependencies:** ```bash npm install ``` 3. **Run tests to verify installation:** ```bash npm test ``` ## Quick Start ### 1. Initialize Your Workspace Create a directory for your notes and navigate to it: ```bash mkdir my-notes cd my-notes ``` ### 2. Set the Command-line Argument When starting the server, use the `--workspace` argument to specify your notes directory: ```bash node src/server.ts --workspace /path/to/your/notes-directory ``` ### 3. Start the MCP Server From the flint-note directory, start the server: ```bash npm start ``` Or for development with auto-reload: ```bash npm run dev ``` ### 4. Configure Your MCP Client Add flint-note to your MCP client configuration. For Claude Desktop, add this to your `claude_desktop_config.json`: ```json { "mcpServers": { "flint-note": { "command": "node", "args": ["/path/to/flint-note/src/server.js", "--workspace", "/path/to/your/notes-directory"] } } } ``` **Note:** You can either use the `env` field in the MCP configuration (as shown above) or rely on the environment variable you set in step 2. The `env` field takes precedence and is useful if you want to use different workspaces for different MCP clients. ### 5. Start Taking Notes! Once connected, you can interact with your notes through natural language: - "Create a new note type for meeting notes" - "Add a note about today's project discussion" - "Search for notes about machine learning" - "Show me all my recent notes" ## Project Structure After initialization, your workspace will look like this: ``` my-notes/ ├── .flint-note/ │ ├── config.yml # Configuration │ ├── search-index.json # Search index │ └── mcp-server.log # Server logs ├── general/ # Default note type │ ├── _description.md # Type definition │ └── welcome.md # Sample note └── [your-note-types]/ # Custom note types ├── _description.md ├── _template.md # Optional template └── your-notes.md ``` ## Configuration The configuration file (`.flint-note/config.yml`) contains: ```yaml version: "1.0.0" workspace_root: "." default_note_type: "general" mcp_server: name: "flint-note" version: "0.1.0" port: 3000 log_level: "info" log_file: ".flint-note/mcp-server.log" search: index_enabled: true index_path: ".flint-note/search-index.json" rebuild_on_startup: false max_results: 50 note_types: auto_create_directories: true require_descriptions: true allow_custom_templates: true ``` ## Available MCP Tools flint-note exposes these tools to AI agents: ### Note Management - `create_note` - Create one or more notes (supports batch operations) - `get_note` - Retrieve a note by identifier - `update_note` - Update one or more existing notes (supports batch operations) - `search_notes` - Search notes by content/type ### Note Type Management - `create_note_type` - Create a new note type with description - `list_note_types` - List all available note types ### Resources - `flint-note://types` - Available note types - `flint-note://recent` - Recently modified notes - `flint-note://stats` - Workspace statistics ## Usage Examples ### Creating Note Types ```bash # Through an AI agent: "Create a note type called 'meetings' for tracking my meeting notes. Include fields for attendees, date, and action items." ``` ### Adding Notes ```bash # Single note through an AI agent: "Add a meeting note for today's team standup. # Batch notes through an AI agent: "Create project notes for Q1: Website Redesign, Mobile App, API Refactor - all due March 31st" Attendees were Alice, Bob, and Charlie. Main topic was the Q4 planning." ``` ### Searching Notes ```bash # Through an AI agent: "Find all notes about project planning from the last month" "Search for notes tagged with 'urgent'" "Show me my recent meeting notes" ``` ## Development ### Running Tests ```bash npm test ``` ### Development Mode ```bash npm run dev ``` ### Project Structure ``` flint-note/ ├── src/ │ ├── server.js # MCP server entry point │ ├── core/ │ │ ├── workspace.js # Workspace management │ │ ├── notes.js # Note operations │ │ ├── note-types.js # Note type management │ │ └── search.js # Search functionality │ └── utils/ │ └── config.js # Configuration utilities ├── test/ # Test files ├── package.json └── README.md ``` ## Troubleshooting ### Common Issues 1. **"Module not found" errors** - Ensure you're using Node.js 18+ with ES modules support - Check that all dependencies are installed with `npm install` 2. **MCP connection issues** - Verify the server is running with `npm start` - Check your MCP client configuration - Look for errors in `.flint-note/mcp-server.log` 3. **Permission errors** - Ensure the user has write permissions to the workspace directory - Check that the `.flint-note` directory can be created 4. **Workspace not found errors** - Verify that the `--workspace` argument is provided correctly - Check that the workspace directory exists and is accessible - Ensure the path is absolute, not relative ### Logs Server logs are stored in `.flint-note/mcp-server.log`. Check this file for detailed error information. ## Security Considerations - flint-note restricts all file operations to within your workspace directory - No external network access is required - All data stays on your local machine - Use version control (git) to backup your notes ## Contributing 1. Fork the repository 2. Create a feature branch 3. Make your changes 4. Add tests for new functionality 5. Submit a pull request ## License MIT License - see LICENSE file for details ## Support For issues and questions: - Check the troubleshooting section above - Review the logs in `.flint-note/mcp-server.log` - Open an issue on the project repository --- *flint-note: Agent-first note-taking for the modern knowledge worker*

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/disnet/flint-note'

If you have feedback or need assistance with the MCP directory API, please join our Discord server