Otto Travel Local

OpenClaw plugin for Otto Travel — search, compare, and book flights and hotels via Otto's MCP endpoint.

Security Scan

The skill's code, instructions, and requirements are consistent with a travel plugin that connects to an MCP server using OAuth device flow and stores tokens locally; nothing in the bundle appears disproportionate or unrelated to that purpose.

Purpose & Capability

Name and description (Otto Travel MCP client) match the code and runtime behavior: the plugin discovers tools from an MCP server, registers them, and calls them. Declared defaults (serverUrl) and the use of @modelcontextprotocol/sdk are coherent with the stated purpose.

Instruction Scope

SKILL.md describes installing the plugin locally and configuring serverUrl. Runtime instructions and code implement an OAuth Device Authorization flow, tool discovery, and tool invocation. The instructions and code only access the MCP server and a local token file; they do not read arbitrary user files, environment variables, or send data to unexpected external endpoints.

Install Mechanism

The registry metadata said 'No install spec — instruction-only', but the package includes source files, package.json, and package-lock.json and the README/SKILL.md instruct installing the plugin locally via openclaw plugins install ./openclaw-otto-travel. There is no network download/install step in the manifest itself. The dependency on @modelcontextprotocol/sdk (and its npm deps) is expected for MCP connectivity; no suspicious remote archives or shorteners are used.

Credentials

The skill requests no environment variables or external credentials in metadata; it implements OAuth device flow and stores tokens to ~/.openclaw/.otto-tokens.json with 0600 permissions. The requested/local persistence of OAuth tokens is proportionate to the plugin's purpose. No unrelated secrets or config paths are requested or accessed.

Persistence & Privilege

always is false and model invocation is allowed (platform default). The plugin persists only its own token file under the user's home directory and does not modify other skills or system-wide settings. This level of persistence is normal for an OAuth-based plugin.

Assessment

This plugin appears to do what it says: it connects to the configured Otto MCP endpoint, runs an OAuth device flow, stores tokens at ~/.openclaw/.otto-tokens.json (0600), and dynamically registers tools. Before installing: (1) Confirm you trust the MCP server URL (default https://api.ottotheagent.com/mcp) — changing it to an untrusted host would let the plugin contact that host and store credentials for it; (2) review the repository/source (package.json points to a GitHub repo) if you want provenance assurance; (3) be aware the plugin depends on the @modelcontextprotocol/sdk and its npm deps (normal for MCP clients); (4) the bundle includes TypeScript source (index.ts) and expects the OpenClaw runtime to load/compile TS — verify your runtime supports this. If any of these are unclear or you don't trust the server URL, do not install.

OpenClaw plugin for Otto Travel — search, compare, and book flights and hotels via Otto's MCP endpoint.

Install

openclaw plugins install ./openclaw-otto-travel

Configuration

In your openclaw.json:

{
  "plugins": {
    "entries": {
      "openclaw-otto-travel": {
        "config": {
          "serverUrl": "https://api.ottotheagent.com/mcp"
        }
      }
    }
  }
}

Tools

Tools are discovered dynamically from the MCP server:

• search_flights / book_flight
• search_hotels / book_hotel
• get_bookings
• Preference and loyalty program management

Security

Uses OAuth 2.1; tokens stored securely at ~/.openclaw/.otto-tokens.json.