> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paperzilla.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent workflows

> Use Paperzilla as a data layer for agent and automation workflows through CLI, feeds, and MCP.

export const AiAgents = ({path}) => <Tip>
    <b>AI agents</b>: This page is available as <a href={path + '.md'}>markdown</a>. See also the <a href="/llms.txt">docs index</a> and <a href="/llms-full.txt">full docs</a>.
  </Tip>;

<AiAgents path="/guides/agent-workflows" />

Paperzilla is designed for both human reading and programmatic use.

This guide focuses on Paperzilla as a **data layer for agents**.

## Available interfaces

Use these depending on your workflow:

* CLI (`pz`) for shell/script execution
* MCP (`/api/mcp`) for LLM tool-calling workflows
* RSS/Atom for polling in feed infrastructure

See [CLI guide](/guides/cli), [MCP integration](/guides/mcp), [Codex guide](/guides/codex), [Claude guide](/guides/claude), and [RSS/Atom guide](/guides/feeds).

## Recommended setup for agent workflows

1. Create and tune projects in the app.
2. Authenticate CLI with `pz login`.
3. Use `pz project list --json` to get the project ID you need from structured output.
4. Use `pz feed <project-id> --json` for browse-style automation, or `pz feed search --project-id <id> --query <q> --json` for text search across the full feed.
5. Add filters (`--must-read`, `--since`, `--limit`, `--feedback-filter`) based on your workflow.

## OpenClaw skill

The Paperzilla CLI is published as an [OpenClaw skill on ClawHub](https://clawhub.ai/pors/paperzilla). Install it with `openclaw skills install paperzilla` to let OpenClaw use `pz` commands directly. If you already use the separate ClawHub CLI, `clawhub install paperzilla` also works. See [Use the Paperzilla CLI with OpenClaw](/guides/openclaw) for the full setup flow.

## Codex

Codex works with Paperzilla in two ways. Add Paperzilla MCP from Codex **Settings** > **Integrations & MCP** when you want native tool calling. Then confirm the server in `/mcp`. Use `pz` directly when Codex already works in a shell or repo. A useful Codex skill should cover setup verification, docs pointers, and the Paperzilla tool sequence, not just "prefer MCP" or "use the CLI." A plugin is only needed when you want an installable package. See [Use Paperzilla with Codex](/guides/codex).

## Data surfaces you can combine

* App feed for visual review
* CLI for structured automation
* RSS/Atom for polling in feed infrastructure
* Email digests for human review cadence

## MCP tool surface

Current tools:

* `projects_list`
* `projects_get`
* `feed_get`
* `feed_search`
* `feed_atom_url`
* `paper_get`
* `paper_markdown`

Optional prompt:

* `feed_title_filter`

Use `feed_search` when your workflow needs text search across an entire project feed. It is the MCP path for search by title, author, abstract, or summary terms.

Setup details: [MCP integration](/guides/mcp).

## Example workflows

* [Use OpenClaw and Telegram for research briefs](/guides/openclaw-telegram-briefs)
* [Use Codex and Microsoft Teams for research briefs](/guides/codex-teams-briefs)
* [Use Claude in Slack for research briefs](/guides/claude-slack-briefs)

## Why this matters

If your workflow depends on "fresh papers + relevance filtering + automation," treat Paperzilla projects as the persistent source and let agents consume that data layer.