rierino

Rierino — Claude Code Plugin

Connect Claude Code to the Rierino low-code development platform. Drop this folder into your project and Claude gains full awareness of the platform — skills, agents, commands, and an authenticated MCP proxy — all with no build step.

Architecture

Claude Code
    │
    ├── reads skills/global/CONVENTIONS.md       (naming & data standards)
    ├── reads skills/global/RULES.md             (operational rules)
    ├── reads skills/<skill>/SKILL.md            (per-task instructions)
    │
    ├── runs /commands/rierino-status            (health check)
    ├── runs /commands/rierino-mcp               (list MCP capabilities)
    │
    └── calls MCP tools ──► whatever the Rierino server registers
                                  │
                        Token vault (AES-256-GCM)
                        Auth layer (JWT login + auto-refresh)
                                  │
                          Rierino MCP Server

The MCP server (proxy.js) is a transparent authenticated proxy — it forwards every JSON-RPC call straight to the Rierino server. Tools are discovered at runtime via tools/list; no tool definitions live in this plugin.

Tokens are encrypted in-memory with an ephemeral AES-256-GCM key. Claude only ever sees opaque masked handles — real JWTs never leave the proxy process.

---

Setup

1. Configure credentials

Security note: Do not store credentials in servers/rierino-mcp/.env or anywhere inside the plugin folder. Claude Code can read files within the project directory, which would expose your username and password in Claude's context. Use one of the two approaches below instead.

Option A — env block in .mcp.json (recommended)

Pass credentials directly in your .mcp.json (or claude_desktop_config.json). This file is read by the Claude Code harness to spawn the MCP server and is not passed to Claude as conversation context.

{
  "mcpServers": {
    "rierino": {
      "command": "node",
      "args": ["[PATH]/servers/rierino-mcp/proxy.js"],
      "env": {
        "RIERINO_BASE_URL": "https://your-instance.rierino.com",
        "RIERINO_USERNAME": "your-username",
        "RIERINO_PASSWORD": "your-password"
      }
    }
  }
}

Add .mcp.json to your .gitignore so credentials are never committed.

Option B — .env file outside the project

Store a .env file in a directory that is not inside your project tree (e.g. ~/.config/rierino/.env) and point cwd to that directory:

{
  "mcpServers": {
    "rierino": {
      "command": "node",
      "args": ["[PATH]/servers/rierino-mcp/proxy.js"],
      "cwd": "/home/you/.config/rierino"
    }
  }
}

proxy.js loads .env from its working directory, so this keeps credentials entirely outside any folder Claude can browse.

2. Project root .env

Create a .env file in your project root (next to .mcp.json) with:

RIERINO_UI_BASE_URL=https://your-instance.rierino.com

This is used by Claude to generate direct links to UI records (e.g. ${RIERINO_UI_BASE_URL}/app/design/common/ui?id={id}). This file contains no credentials — only a public base URL — so it is safe to keep inside the project.

Add .env to your .gitignore.

No npm install or build step — proxy.js has zero external dependencies.

3. Verify

> /rierino-status
> /rierino-mcp tools

---

What's included