UB UrBrain

Plugin marketplace

Runtime integrations you can review publicly and install from your dashboard.

UrBrain plugins are productized integrations, not hidden backend toggles. Public catalog pages make each plugin discoverable and reviewable. The dashboard store adds account authorization, paid entitlements, workspace install state, configuration, health, and credential rotation.

Plugin marketplace

Public catalog, dashboard install flow.

The public site exposes indexable plugin pages and reviewable permission metadata. The dashboard adds workspace identity, paid entitlement checks, install state, configuration, health, and credential rotation.

Public catalog

SEO-friendly static projection

Ur Brain

Claude Code

First-party available Paid plugin

Passive Claude Code runtime capture for Ur Brain.

Captures compact summaries, session outcomes, and selected runtime evidence from Claude Code without turning transcripts into unreviewed authored memory.

Runtime
Ruby, Shell, MCP
Install
Local command, MCP-only
Data
Agent session, Tool call, Compact summary, Session outcome
documents_write Submit redacted Claude Code session evidence and compact summaries as scoped memory inputs.
documents_read Read plugin status and reconnect context for the configured workspace when enabled.
Setup guidance
  1. Install the plugin package on the machine where Claude Code runs.
  2. Open the authenticated UrBrain dashboard for the target workspace.
  3. Rotate plugin credentials and copy the generated environment variables.
  4. Install Claude Code hooks that invoke the plugin command for supported events.
UR_BRAIN_CLAUDE_CODE_API_KEY=<generated> ur_brain-claude-code hook <event>

plugin_claude_code Requires paid workspace access

Open in dashboard Review details

Ur Brain

OpenClaw

First-party planned Paid plugin

Passive OpenClaw runtime capture and future case-memory evidence.

A planned runtime bridge for OpenClaw and Pi seams, starting with observe-only evidence and growing toward deeper memory portability where the runtime exposes stable boundaries.

Runtime
TypeScript, MCP
Install
Local command, MCP-only
Data
Agent session, Tool call, Compact summary, Session outcome
documents_write Submit redacted runtime evidence as scoped memory inputs.
Setup guidance
  1. Review the planned OpenClaw runtime integration mode.
  2. Wait for the dashboard store to mark the plugin available.
  3. Install from the authenticated workspace once setup commands are generated.
Generated after the plugin is available.

Not installable yet Visible for roadmap review

Preview Review details

Ur Brain

Hermes

First-party planned Paid plugin

Hosted and Python-agent runtime evidence bridge.

A planned bridge for hosted and Python-agent runtime evidence, with MCP-only and hosted connector install paths.

Runtime
Python, MCP
Install
Hosted connector, MCP-only
Data
Agent session, Tool call, Compact summary, Session outcome
documents_write Submit hosted agent evidence as scoped memory inputs.
documents_read Read scoped memory context for configured hosted agents.
Setup guidance
  1. Review hosted connector permissions and data classes.
  2. Connect through the dashboard when the Hermes plugin becomes available.
  3. Use dashboard-generated credentials for the selected workspace.
Generated after the plugin is available.

Not installable yet Visible for roadmap review

Preview Review details

Ur Brain

Paperclip

First-party planned Paid plugin

File and artifact capture bridge for large external evidence payloads.

A planned sidecar for file-backed evidence, artifacts, and payloads that should stay addressable without forcing large blobs into ordinary retrieval context.

Runtime
Ruby, Shell
Install
Local command, Sidecar
Data
Document, Artifact, External payload
documents_write Submit file-backed evidence and artifact metadata.
Setup guidance
  1. Review artifact and external payload handling before install.
  2. Install the sidecar from the authenticated dashboard once available.
  3. Use dashboard-generated storage and workspace credentials.
Generated after the plugin is available.

Not installable yet Visible for roadmap review

Preview Review details

One catalog, two contexts

The static site should publish the same plugin facts the dashboard uses: name, runtime targets, install modes, permissions, data classes, billing SKU, and trust state. In the dashboard, the same component can receive workspace state and progressively reveal install, configure, health, and credential controls.