Skip to main content
Glama
ShakeLv

remio-harness-plugin

by ShakeLv
README.md
# remio Harness Plugin

[MCP](https://modelcontextprotocol.io/) server for using a local [remio](https://remio.ai) knowledge base from DeepSeek Harness and any MCP-compatible agent client.

It exposes remio search, reading, RAG, web retrieval, note management, collection management, sync-folder management, public sharing, agent execution, and advanced syscalls. It invokes the local `remio` executable directly with argument arrays; it never opens a shell.

## Requirements

- Node.js 20 or later
- pnpm (required by `dsh plugin`)
- remio desktop app installed and running
- remio CLI available on `PATH` (or set `REMIO_CLI_PATH`)

## Install

After the package is published, install it in a DeepSeek Harness profile:

```bash
dsh plugin --profile standard add @remio/harness-plugin
```

DSH loads the bundle automatically and exposes the remio MCP tools under the `mcp__remio__` namespace, for example `mcp__remio__remio_search_notes` and `mcp__remio__remio_ask`.

The same published package can also be used directly by any MCP-compatible client:

```json
{
  "mcpServers": {
    "remio": {
      "command": "npx",
      "args": ["-y", "@remio/harness-plugin"]
    }
  }
}
```

For local development:

```bash
npm install
npm run build
node dist/index.js
```

```json
{
  "mcpServers": {
    "remio": {
      "command": "node",
      "args": ["/absolute/path/to/remio-harness-plugin/dist/index.js"]
    }
  }
}
```

## Tools

| Tool | Purpose | Confirmation |
| --- | --- | --- |
| `remio_help` | Local CLI usage | No |
| `remio_search_notes` | Search the knowledge base | No |
| `remio_read` | Read a note or supported local file | No |
| `remio_ask` | RAG answer with citations | No |
| `remio_web` | Commercial web search or clean web extraction | No |
| `remio_notes` | Create, update, delete, attach images, status, permissions | Required |
| `remio_collections` | Add or remove a note from a collection | Required |
| `remio_sync_folders` | List or manage indexed folders | Required for changes |
| `remio_share` | Publish, refresh, or revoke a public note link | Required |
| `remio_run_agent` | Run a remio Agent task | Required |
| `remio_syscall` | Advanced remio syscall escape hatch | Required |
| `remio_cli` | Full CLI compatibility entry point | Required for changes |

The structured tools are the recommended interface. `remio_cli` is retained for a remio CLI capability that has not yet been promoted into a dedicated structured tool.

## Safety model

The server uses MCP tool annotations so compatible clients can show appropriate risk prompts. It additionally refuses every state-changing call unless the caller sends `confirm: true` after obtaining explicit user approval.

The server does not bypass remio authorization. Existing remio restrictions, passwords, session-scoped write checks, and public-sharing behavior remain enforced by the local remio app.

## Configuration

| Variable | Meaning | Default |
| --- | --- | --- |
| `REMIO_CLI_PATH` | Absolute path to the remio executable | `remio` |
| `REMIO_CLI_TIMEOUT_MS` | CLI invocation timeout | `120000` |

## Development and release

```bash
npm ci
npm run check
npm test
npm run pack:check
```

The CI workflow verifies Node.js 20, 22, and 24. Before the first public release, add the canonical public repository URL to `package.json`, publish under the `@remio` npm organization, and submit the npm package plus repository link to the applicable Harness plugin directory. DSH detects the package as a native profile bundle through its `dsh.bundle.patch` manifest field.

The DSH bundle has been verified against `@deepseek-ai/dsh@0.1.0-rc.6`: a clean profile installed the package successfully and its composed configuration included the `remio-mcp` bridge row.

## License

MIT

TDQS

A3.6/5.0

Scored across 12 tools

Disambiguation3/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness5/5

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.

Maintenance

ActivitySlowing
ResponsivenessNo issues