CipherNote MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CIPHERNOTE_DB | No | 可选。自定义 SQLite 数据库路径。 | 系统本地数据目录 |
| CIPHERNOTE_KEY | Yes | 必需。32 字节密钥,必须使用 base64: 或 hex: 前缀。 | |
| CIPHERNOTE_PYTHON | No | 可选。自定义 Python 可执行文件。 | Windows 使用 python,其他系统使用 python3 |
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 |
|---|---|
| private_note_writeC | Write an encrypted local note. Do not use it for passwords, tokens, or other credentials. |
| private_note_searchC | Search encrypted notes locally. |
| private_note_readC | Read one encrypted note by ID. |
| private_note_recentB | List recent note metadata without returning note bodies. |
| private_note_deleteC | Permanently delete one note by ID. |
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 5 tools
Each tool has a clearly distinct action: write creates a note, read retrieves one by ID, search queries notes, recent lists metadata, and delete removes a note. The search/recent distinction is explicitly clarified by recent returning metadata only, so there is little risk of misselection.
All tools consistently use the private_note_ prefix with snake_case suffixes, making the set easy to scan. The only minor deviation is that recent is an adjective rather than a verb, while the others follow an action-oriented pattern.
Five tools are well-scoped for a focused encrypted-notes server and each operation earns its place. The set avoids redundant listing or administrative tools that would bloat the surface.
The surface covers creation, retrieval, search, recent listing, and deletion, which supports most note workflows. However, there is no update/edit operation, forcing agents to delete and recreate notes to modify content, which is a notable lifecycle gap.