NoteDiscovery MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTEDISCOVERY_URL | No | The URL of the NoteDiscovery instance | http://localhost:8000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_notesA | Search through all notes using full-text search. Returns matching notes with snippets showing where the match was found. Use this to find notes by content, keywords, or phrases. |
| list_notesA | List all notes in the knowledge base with their metadata (title, path, last modified date, size). Use this to get an overview of available notes or find notes by browsing. |
| get_noteA | Read the full content of a specific note by its path. Returns the complete markdown content along with metadata. Use this after finding a note via search or list to read its contents. |
| list_tagsA | List all tags used across notes with the count of notes for each tag. Use this to understand how notes are organized and find topics. |
| get_notes_by_tagB | Get all notes that have a specific tag. Use this to find related notes on a topic. |
| get_graphA | Get the knowledge graph showing relationships between notes. Returns nodes (notes) and edges (links between them). Use this to understand how notes connect to each other. |
| get_backlinksA | Get all notes that link TO a specific note (backlinks/reverse links). Use this to discover what other notes reference the current note, helping understand its importance and connections in the knowledge base. |
| create_noteA | Create a new note or update an existing one. The note will be saved as a markdown file. Use this to save new information or update existing notes. |
| delete_noteA | Delete a note permanently. Use with caution - this cannot be undone. |
| create_folderB | Create a new folder for organizing notes. |
| append_to_noteA | Append content to an existing note without overwriting. Perfect for journals, logs, meeting notes, or collecting ideas incrementally. |
| move_noteA | Move or rename a note to a different path. Use this to reorganize notes or rename them. |
| get_recent_notesA | Get recently modified notes. Useful for finding what you were working on recently. |
| create_note_from_templateA | Create a new note from a template. Built-in placeholders like {{title}}, {{date}}, {{datetime}}, {{folder}}, {{date:FMT}} are substituted automatically (FMT is a Python strftime string). Use update_note afterwards if you need to inject custom content. |
| list_templatesB | List available note templates. Templates provide pre-formatted structures for common note types. |
| get_templateA | Get the content of a specific template. Use this to see what a template contains before using it. |
| health_checkA | Check if NoteDiscovery server is running and healthy. Use this to verify connectivity. |
| get_configA | Get NoteDiscovery server configuration: app name, version, whether search is enabled, authentication mode, autosave delay. Useful for confirming what server you're connected to and what features are available before calling other tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool has a clearly distinct purpose: note creation and update (create_note, append_to_note, create_note_from_template), deletion, retrieval, search, listing, tags, backlinks, graph, templates, folders, configuration, and health check. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_note, get_note, list_notes, search_notes). The naming is predictable and easy to understand.
With 18 tools, the server covers all essential note-taking operations without being bloated. The count is well-scoped for a complete knowledge management system.
The tool surface covers full CRUD (create, read, update, delete), search, tagging, backlinks, graph visualization, templates, folder management, and server configuration. There are no obvious gaps for typical note-taking workflows.