tilnote-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TILNOTE_API_KEY | Yes | Your Tilnote API key |
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
| Name | Description |
|---|---|
| create_noteB | Create a markdown note on Tilnote. The note is saved as a draft. |
| get_noteB | Get the full content of a specific Tilnote note by its page ID. |
| list_notesA | List your Tilnote notes. Returns recent notes with title, excerpt, and URL. |
| search_notesA | Search your Tilnote notes by keyword (searches title and content). |
| update_noteB | Update the title or content of an existing Tilnote note. |
| create_bookB | Create a new book on Tilnote. Returns the book ID and URL. |
| list_booksB | List your Tilnote books. Returns title, page count, and URL for each book. |
| get_bookA | Get details of a specific Tilnote book including its list of pages. |
| add_page_to_bookB | Add an existing note (page) to a Tilnote book. |
| remove_page_from_bookB | Remove a note (page) from a Tilnote book. |
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 10 tools
Each tool targets a distinct action on either notes or books, with no overlap. For example, create_note and update_note are clearly separate, and add_page_to_book/remove_page_from_book are specific to book-page relationships.
All tools follow a consistent verb_noun pattern (e.g., create_book, list_notes, get_note, search_notes), making it predictable and easy for an agent to infer functionality.
With 10 tools, the set is well-scoped for a note-taking and book organization domain. It covers core operations without being excessively large or too minimal.
While the tool set covers creation, retrieval, and updates, it lacks delete operations for notes and books (no delete_note, delete_book). This is a notable gap that may cause dead ends in workflows requiring removal.