malv overview

Get a quick view of what your apps expose - storage paths, tokens, tools, and objects.

Usage

# Show everything for all apps
malv overview

# Show specific apps
malv overview @my-org/auth @my-org/notes

# Show only certain sections
malv overview --storage
malv overview --tokens
malv overview --tools
malv overview --objects

# Combine filters
malv overview --tokens @my-org/auth

What It Shows

The command reads your apps' configuration files and displays a formatted summary.

Storage Paths

Shows declared storage permissions:

@my-org/notes
  Storage:
    📁 /notes/<token.accountId>/     [read, write, list]
    📁 /shared/<token.teamId>/       [read]

Tokens

Shows token definitions:

@my-org/auth
  Tokens:
    🎫 account
       State: "Signed in"
       Fields: accountId, email, role
       Expires: 30 days

Tools

Shows available tools:

@my-org/notes
  Tools:
    🔧 create_note - Creates a new note with title and content
    🔧 edit_note - Updates an existing note
    🔧 list_notes - Lists all notes for the current user
    🔧 delete_note - Removes a note

Hidden tools (prefixed with _) are counted but not listed.

Objects

Shows object definitions:

@my-org/notes
  Objects:
    📦 note-editor
       Title: "Note"
       Renders: web
       Capabilities: storage, tool

Options

Option Short What It Does
--storage -s Show only storage paths
--tokens -t Show only tokens
--tools -T Show only tools
--objects -o Show only objects
--filter -f Filter to specific apps

From App Directory

If you run malv overview from inside an app directory (one with tools.json), it shows just that app:

cd packages/apps/notes
malv overview

This is handy when you're focused on a single app.

Use Cases

Checking what's available

Before using an app's tools, see what they do:

malv overview @my-org/email --tools

Reviewing permissions

Check what storage paths an app can access:

malv overview @my-org/notes --storage

Understanding token flow

See what tokens exist and what apps issue them:

malv overview --tokens