textview-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEXTVIEW_TOKEN | Yes | API token (starts with 'tv_'), generated at textview.cn |
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 |
|---|---|
| save_documentA | 保存新文档到 TextView。content 必须为 HTML 格式(不要用 Markdown)。例: 标题段落列表项 |
| list_documentsB | 列出 TextView 中的文档,按更新时间倒序排列。 |
| get_documentC | 获取单个文档的完整内容。 |
| update_documentB | 更新已有文档的标题或内容。至少提供 title 或 content 之一。content 必须为 HTML 格式(不要用 Markdown)。 |
| save_memoA | 保存一条碎片记录到 TextView 记录区。适用于快速笔记、语音转文字、剪贴板内容等碎片化信息。 |
| list_memosC | 查询 TextView 记录区的碎片记录,按时间倒序。 |
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 6 tools
Tools are cleanly partitioned into document operations (save/list/get/update) and memo operations (save/list). save vs update is distinguished by creating a new document versus modifying an existing one, and document vs memo is distinguished by structured HTML documents versus fragmented notes. No overlapping purposes are apparent.
All names use snake_case with a consistent verb_noun structure (save_, list_, get_, update_). The only minor variation is plural nouns for list operations versus singular for single-resource operations, which is conventional and readable.
Six tools for a document and memo management server is well-scoped, with each operation serving a distinct purpose. The surface is not bloated or thin for the apparent scope.
Document lifecycle supports create, read, update, and list but has no delete operation, leaving a dead end for removing documents. Memos only support save and list, with no get/update/delete, so lifecycle coverage is notably incomplete.