MCP Quickstart

​

Prerequisites

• A Rastro account at dashboard.rastro.ai
• uv installed (curl -LsSf https://astral.sh/uv/install.sh | sh)

​

Authenticate

uvx rastro.ai login

​

Configure your client

claude mcp add rastro -- uvx rastro.ai

claude mcp add rastro \
  -e RASTRO_API_KEY=rastro_pk_... \
  -- uvx rastro.ai

{
  "mcpServers": {
    "rastro": {
      "command": "uvx",
      "args": ["rastro.ai"]
    }
  }
}

{
  "mcpServers": {
    "rastro": {
      "command": "uvx",
      "args": ["rastro.ai"],
      "env": {
        "RASTRO_API_KEY": "rastro_pk_..."
      }
    }
  }
}

{
  "mcpServers": {
    "rastro": {
      "command": "uvx",
      "args": ["rastro.ai"]
    }
  }
}

"env": {
  "RASTRO_API_KEY": "rastro_pk_..."
}

[mcp_servers.rastro]
command = "uvx"
args = ["rastro.ai"]

[mcp_servers.rastro]
command = "uvx"
args = ["rastro.ai"]
env = { RASTRO_API_KEY = "rastro_pk_..." }

​

Verify

List my Rastro catalogs

​

First workflow

For catalog <catalog_id>, pull a snapshot, update price/cost by my rules,
compute diff, validate, and stage one pending-review activity.
Do not apply automatically.

1. execution_catalog_snapshot_pull
2. Local transform (agent-generated Python)
3. execution_local_diff_compute
4. execution_bundle_validate
5. catalog_activity_create_transform (or execution_catalog_stage_dataset)
6. Review and apply in the dashboard

​

Safety defaults

• Programmatic approve/apply is blocked — all changes require dashboard review.
• Large change sets are staged into one activity (chunked internally).
• Always review the dashboard diff before applying.

​

Next