NoteKing MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTEKING_API_KEY | No | Optional Bearer token for authentication. | |
| NOTEKING_API_URL | No | NoteKing API base URL. | http://localhost:3000 |
| NOTEKING_TIMEOUT_MS | No | HTTP request timeout in milliseconds. | 30000 |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| noteking_list_projectsB | List and search note projects / workspaces in NoteKing with note count metrics and pagination |
| noteking_get_projectB | Get full project details including its associated note list index and metadata |
| noteking_create_projectC | Create a new note project workspace in NoteKing |
| noteking_update_projectC | Update an existing project's name or description in NoteKing |
| noteking_delete_projectB | Delete a project from NoteKing (notes belonging to this project are preserved as standalone notes) |
| noteking_list_notesB | List, filter, and search notes in NoteKing by full-text query, project, standalone scope, or pinned status |
| noteking_get_noteB | Retrieve a note's full Markdown content, metadata, attachments, and optional rendered HTML |
| noteking_create_noteB | Create a new Markdown note in NoteKing (under a project or as a standalone scratchpad note) |
| noteking_update_noteC | Update a note's title, Markdown body, project assignment, or pinned status |
| noteking_append_to_noteA | Safely append a Markdown section or log entry to the end of an existing note without overwriting its prior body |
| noteking_delete_noteB | Permanently delete a note and its attachments from NoteKing |
| noteking_toggle_pinC | Toggle the pinned status of a note on the NoteKing sidebar |
| noteking_reorder_pinnedC | Update the sequential order of pinned notes displayed in the NoteKing sidebar |
| noteking_list_attachmentsC | List file attachments associated with a note |
| noteking_upload_attachmentB | Upload one or more files to attach to a note in NoteKing (accepts local file paths or base64 data) |
| noteking_delete_attachmentC | Purge and delete an attachment from a note |
| noteking_render_markdownB | Render Markdown text to sanitized HTML using NoteKing's GitHub-flavored markdown pipeline |
| noteking_get_statsA | Get system statistics from NoteKing (total notes, standalone notes, pinned notes, projects, and attachments) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| noteking_use_note_template | Load any NoteKing note or template by ID, substituting {{variables}} into the Markdown body |
| noteking_author_note | Interactive engineering guide to draft structured technical notes, ADRs, runbooks, or meeting notes for NoteKing |
| noteking_summarize_project | Fetch a NoteKing project and all its associated notes to synthesize an executive overview, ADR index, and open items |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| noteking_stats | Aggregated NoteKing statistics: total notes, standalone notes, pinned notes, projects, and attachments |
| noteking_projects | Index of all active project workspaces in NoteKing |
| noteking_notes | Index of all notes currently saved in NoteKing |
TDQS
Scored across 18 tools
Most tools target distinct resources and actions, and the note/project/attachment boundaries are clear. Minor overlap exists: update_note can also change pinned status while toggle_pin exists, and get_note returns attachment info while list_attachments is a separate tool.
All tools follow a consistent noteking_verb_noun snake_case pattern. Variants like append_to_note, toggle_pin, and render_markdown still fit the same predictable convention.
The 18-tool surface is somewhat large but reasonable for a full note workspace covering notes, projects, attachments, pinning, stats, and markdown rendering. A few tools could be consolidated, but each broadly earns its place.
CRUD coverage for notes and projects is strong, with useful extras like append, pinning, stats, and rendering. The main gap is attachment retrieval/download: attachments can be listed, uploaded, and deleted, but their content cannot be fetched directly.