NotesKeep MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTESKEEP_API_KEY | Yes | Your NotesKeep API key | |
| NOTESKEEP_API_URL | No | Custom API URL (defaults to https://noteskeep.vercel.app) | https://noteskeep.vercel.app |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
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 14 tools
Every tool has a clearly distinct purpose targeting specific note or label operations with no ambiguity. For example, 'add_label_to_note' and 'remove_label_from_note' are complementary but distinct actions, while 'get_note_labels' and 'set_note_labels' serve different query vs. modification functions.
All tools follow a consistent verb_noun pattern with snake_case throughout, such as 'create_note', 'delete_label', and 'list_notes'. The naming is predictable and readable, with no deviations in style or convention across the set.
With 14 tools, this server is well-scoped for a notes management domain, covering CRUD operations for notes and labels, plus additional utilities like archiving and pinning. Each tool earns its place without feeling excessive or insufficient for the apparent functionality.
The tool set provides complete CRUD/lifecycle coverage for notes and labels, including creation, retrieval, updating, deletion, listing, and specialized actions like archiving and pinning. There are no obvious gaps, and agents can handle full workflows without dead ends.