Sidvy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | false |
| SIDVY_API_URL | No | API base URL | https://sidvy.com/api |
| SIDVY_API_TOKEN | Yes | Your JWT authentication token (required) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notesB | List notes with optional filtering and search capabilities |
| create_noteC | Create a new note with markdown content |
| update_noteC | Update an existing note's content or metadata |
| delete_noteB | Delete a note (moves to trash) |
| search_notesB | Search notes by content or title with full-text search |
| get_noteB | Get a specific note by ID |
| get_recent_notesB | Get recently updated notes |
| append_to_noteC | Append content to an existing note |
| list_groupsC | List groups with hierarchical structure and filtering |
| create_groupC | Create a new group for organizing notes |
| update_groupC | Update a group's name or move it in the hierarchy |
| delete_groupA | Delete a group and all its child groups (cascade delete) |
| get_group_treeA | Get the hierarchical tree structure of all groups in a workspace |
| get_root_groupsC | Get all root-level groups (groups with no parent) |
| get_child_groupsB | Get all child groups of a specific parent group |
| get_group_pathC | Get the full path from root to a specific group |
| move_groupC | Move a group to a new parent (or to root level) |
| create_group_pathA | Create a nested group structure from a path (creates missing parent groups) |
| list_todosC | List todos with filtering options (by completion status, note, etc.) |
| create_todoC | Create a new todo associated with a note |
| update_todoC | Update a todo's text, completion status, or line number |
| delete_todoB | Delete a todo (soft delete) |
| toggle_todoB | Toggle a todo's completion status (complete <-> incomplete) |
| complete_todoB | Mark a todo as completed |
| uncomplete_todoC | Mark a todo as incomplete |
| get_pending_todosC | Get all incomplete/pending todos |
| get_completed_todosC | Get all completed todos |
| get_todos_for_noteC | Get all todos associated with a specific note |
| get_todo_statsB | Get statistics about todos (total, completed, pending, completion rate) |
| search_todosC | Search todos by text content |
| create_todos_for_noteC | Create multiple todos for a note at once |
| list_workspacesB | List all workspaces for the authenticated user with content counts |
| create_workspaceA | Create a new workspace (max 2 workspaces per user) |
| update_workspaceC | Update a workspace (currently only name changes supported) |
| delete_workspaceA | Delete a workspace and all its content (cannot delete default workspace) |
| get_workspaceC | Get details of a specific workspace |
| get_default_workspaceB | Get the user's default workspace |
| get_workspace_by_nameB | Find a workspace by its name |
| get_workspace_statsC | Get detailed statistics for a workspace |
| can_create_workspaceA | Check if the user can create another workspace (max 2 allowed) |
| switch_workspaceB | Switch context to a different workspace (for subsequent operations) |
| rename_workspaceC | Rename an existing workspace |
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 42 tools
Most tools have distinct purposes, but some overlap exists: 'complete_todo', 'toggle_todo', and 'uncomplete_todo' all manage todo completion status, which could cause confusion. Similarly, 'get_pending_todos' and 'list_todos' with filtering might overlap. However, descriptions clarify differences, and other tools like 'create_group' vs. 'create_group_path' are well-differentiated.
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly. Verbs are clear and predictable (e.g., create_, get_, list_, update_, delete_, search_), with no mixing of conventions or chaotic naming. This makes the set easy to navigate and understand.
With 42 tools, the count is excessive for a note and todo management server, making it feel heavy and potentially overwhelming. A more focused set of 10-20 tools could cover the same domain without redundancy, as many tools (e.g., multiple todo status tools) could be consolidated into fewer, more versatile ones.
The tool surface provides comprehensive CRUD and lifecycle coverage for notes, todos, groups, and workspaces, with no obvious gaps. It includes creation, retrieval, updating, deletion, searching, and specialized operations like statistics and hierarchical management, ensuring agents can handle all core workflows without dead ends.