MyMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SYNOLOGY_URL | No | URL of the Synology NAS (e.g., http://NAS_IP:5000) | |
| SYNOLOGY_PASSWORD | No | Password for Synology login | |
| SYNOLOGY_USERNAME | No | Username for Synology login |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_chrome_historyA | 依關鍵字搜尋 Chrome 瀏覽歷史紀錄。 會比對網頁標題和 URL。 Args: keyword: 搜尋關鍵字 max_results: 最大回傳筆數（預設 100） |
| get_recent_historyA | 取得最近 N 小時內的 Chrome 瀏覽紀錄。 Args: hours: 回溯的小時數（預設 24 小時） max_results: 最大回傳筆數（預設 100） |
| search_chrome_bookmarksA | 依關鍵字搜尋 Chrome 書籤。 會比對書籤名稱和 URL。 Args: keyword: 搜尋關鍵字 |
| list_chrome_bookmark_foldersA | 列出所有 Chrome 書籤資料夾及其包含的書籤數量。 |
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 4 tools
Each tool targets a distinct resource and action: history search, time-based history retrieval, bookmark search, and bookmark folder listing. There is no overlap in purpose, so an agent can easily select the right tool.
All tool names follow a consistent verb_noun pattern in snake_case (search_chrome_history, get_recent_history, search_chrome_bookmarks, list_chrome_bookmark_folders). Minor variation in whether 'chrome' appears is acceptable and doesn't confuse the pattern.
With 4 tools, the server is tightly scoped to Chrome history and bookmark retrieval. Each tool serves a clear purpose, and the count is ideal for a focused utility server.
The server covers the main read operations for Chrome history and bookmarks: searching, recent retrieval, and folder listing. Missing are operations like fetching all bookmarks or bookmark details, but these are minor gaps for the stated purpose.