remio-harness-plugin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REMIO_CLI_PATH | No | Absolute path to the remio executable | remio |
| REMIO_CLI_TIMEOUT_MS | No | CLI invocation timeout | 120000 |
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 |
|---|---|
| remio_helpB | Returns the authoritative usage for a locally installed remio CLI command. |
| remio_search_notesA | Search notes, files, email, Slack, meetings, and other remio knowledge. Prefer this before reading a note by ID. |
| remio_readA | Reads a remio note by note ID, or converts a local supported file to markdown. Do not read unrelated local files. |
| remio_askB | Answers a question from the remio knowledge base and includes note citations when available. |
| remio_webA | Uses remio's configured high-quality web search or clean web-page extraction. Fetching never creates a remio note. |
| remio_notesC | Changes notes, people notes, note images, permissions, or status. Requires explicit confirmation for every call. |
| remio_collectionsA | Adds or removes a note from a collection. Adding by collection title creates that collection when it does not exist. |
| remio_sync_foldersB | Lists or changes folders that remio indexes. Changes require explicit confirmation; removing a folder preserves already-created notes. |
| remio_shareA | Publishes a note to a public URL, refreshes an existing public URL, or revokes public access. Requires explicit confirmation. |
| remio_run_agentB | Runs a remio Agent with a project directory. It may invoke the requested capabilities, so explicit confirmation is required. |
| remio_syscallA | Advanced escape hatch for a remio syscall not represented above. It can have arbitrary side effects and always requires explicit confirmation. |
| remio_cliA | Compatibility entry point for every remio CLI command: search_notes, read_note, read_file, add_sync_folder, list_sync_folders, pause_sync_folder, resume_sync_folder, remove_sync_folder, create_note, update_note, attach_image, add_note_to_collection, remove_note_from_collection, delete_note, update_note_restrictions, share_note, unshare_note, set_note_status, create_people_note, rag, web_search, web_get, run_agent, syscall. Prefer the structured tools above. State-changing commands require confirm: true. |
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 12 tools
Most tools have distinct purposes, but remio_search_notes, remio_ask, and remio_web all involve retrieving information, and remio_cli/remio_syscall are catch-alls that overlap with every other tool. The descriptions help clarify, but some ambiguity remains.
All tools share the remio_ prefix and most use verb-based names (help, search_notes, read, ask, share, run_agent), though a few are nouns (notes, collections, web). The overall pattern is consistent and predictable.
Twelve tools is well within the optimal range and appropriate for a knowledge-management integration. Each tool covers a distinct capability, with the CLI and syscall tools providing fallbacks.
The surface covers searching, reading, asking, web access, note creation/updating, collections, folder sync, sharing, and agent execution. The remio_cli tool exposes every CLI command, so there are no obvious dead ends.