shiori-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHIORI_TIMEOUT | No | HTTP timeout in seconds, default 20 | |
| SHIORI_BASE_URL | No | Base URL of the Shiori instance, e.g. https://shiori.example.com | |
| SHIORI_PASSWORD | No | Shiori password | |
| SHIORI_USERNAME | No | Shiori username | |
| SHIORI_SESSION_ID | No | Existing Shiori session id; skips login if provided |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| shiori_health_checkA | Verify Shiori API connectivity and authentication with a small read-only request. |
| shiori_list_bookmarksC | List Shiori bookmarks from the default Shiori bookmarks endpoint. |
| shiori_search_bookmarksB | Search Shiori bookmarks client-side by text and/or tag. |
| shiori_get_bookmarkB | Get one Shiori bookmark by id from the bookmark list. |
| shiori_get_bookmark_by_urlA | Get one Shiori bookmark by exact URL from the bookmark list. |
| shiori_add_bookmarkB | Add a bookmark to Shiori. |
| shiori_update_bookmarkC | Update a Shiori bookmark using the full bookmark JSON object expected by the legacy API. |
| shiori_update_bookmark_fieldsA | Patch common bookmark fields by fetching the current bookmark, modifying it, then sending Shiori's full update payload. |
| shiori_delete_bookmarkB | Delete one Shiori bookmark by id. |
| shiori_delete_bookmarksB | Delete one or more bookmarks by id. |
| shiori_list_tagsA | List Shiori tags and bookmark counts. |
| shiori_rename_tagB | Rename a Shiori tag. |
| shiori_list_accountsA | List Shiori user accounts visible to the authenticated session. |
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 13 tools
Most tools target distinct resources and actions, but update_bookmark and update_bookmark_fields could be confused, as could get_bookmark_by_url and search_bookmarks when looking for a URL. The descriptions mostly clarify the boundaries, so misselection risk is modest.
Tool names follow a mostly consistent shiori_<verb>_<noun> snake_case pattern. The main deviation is shiori_health_check, which reads as a noun phrase rather than verb_noun, but the overall naming style is still predictable and uniform.
13 tools is well within the recommended range for a bookmark manager. Each tool covers a meaningful operation without feeling redundant, and the set is neither too thin nor overweighted.
The tool set covers bookmark CRUD, search, bulk deletion, tag listing/renaming, and account visibility, leaving no obvious dead ends for the core domain. Tag creation and deletion are naturally handled through bookmark updates, so the lifecycle appears complete.