PortentDevRequest access
Docs / Get started

Install it where you already work

Portent ships as a Claude Code plugin: a read-only MCP server with recall tools over the knowledge substrates. Start by asking it what it knows; the orchestration lanes open up from there.

Install as a Claude Code plugin

One command registers the recall tools. The server is read-only: it reads the corpus and does not touch your infrastructure until you move to a plan or orchestrate lane and approve each step.

shell
# add the Portent MCP server
claude mcp add portent -- npx -y @portent/mcp@latest

# confirm it registered
claude mcp list

@portent/mcp is a placeholder package name; replace with the real one once published.

Quickstart

Three steps to your first recall

  1. 01

    Add Portent

    Register the read-only Portent MCP server with your Claude Code install. It exposes recall tools over the knowledge substrates, with no write access to your infrastructure.

    shell
    claude mcp add portent -- npx -y @portent/mcp@latest
  2. 02

    Recall before you act

    Ask the corpus what it already knows about your target before you touch anything. Every answer comes back attributed to the run that taught it.

    in Claude Code
    /recall "known EFA misconfigs before a cluster bring-up"
  3. 03

    Read the provenance-backed answer

    You get attributed lessons and, where a number is involved, a provenance stamp: commit, image, command, timestamp. No number ships without one.

    output
    → 3 lessons · L6 fabric · substrate=EFA · all attributed
Reference

Slash commands

The current surface is read-only recall over the corpus. Planning and orchestration lanes add commands that still stop for a human at every irreversible step.

commandwhat it does
/recall <query>Retrieve attributed lessons matching a query. Read-only; no side effects.
/lessons --layer L6 --substrate EFAFilter the corpus by any of the four axes: layer, substrate, framework, subject.
/provenance <metric>Show the full provenance stamp behind a published number: commit, image, command, timestamp.
/plan <goal>Draft a bring-up plan from a goal sentence. Produces a reviewable plan; runs nothing.

Deeper reference (tool schemas, substrate tagging, the coverage ratchet) is coming with the public release.