rapadura hotsites · PHP Com Rapadura Português

Connecting an agent

rapadura exposes the same operations three ways. Pick the one that matches where the agent runs.

1. CLI (any agent that can run commands)

Install, log in once, then every command works with --json:

rapadura login
rapadura publish ./dist --site meetup-sobral --create --json
rapadura sites list --json
rapadura rollback meetup-sobral 3 --json

Errors go to stderr as {"error":{"code":"…","message":"…","hint":"…"}} with exit status 1. Codes are stable; see errors.md.

For CI or an agent without an interactive login, set RAPADURA_TOKEN (and optionally RAPADURA_GATEWAY) in the environment instead of a credentials file.

2. Local MCP over stdio (Claude Code, Cursor, Codex, …)

The CLI is also an MCP server. It uses the saved login and can upload local directories:

claude mcp add rapadura -- rapadura mcp

Tools: whoami, list_zones, list_sites, show_site, create_site, publish_site (with path or inline files), list_versions, rollback_site, delete_site, site_logs; WordPress lane: list_blueprints, create_wp_site, wp_cli, wp_credentials, wp_reset_password.

3. Hosted MCP (no install)

The gateway serves Streamable HTTP MCP at https://agents.rapadura.net/mcp with a bearer token. Get a token with rapadura login on any machine, or ask the owner for one, then:

claude mcp add --transport http rapadura https://agents.rapadura.net/mcp \
  --header "Authorization: Bearer rpd_…"

On the hosted lane publish_site takes files inline (files: [{path, content}], base64 for binaries) since the gateway cannot read your disk. OAuth sign-in for clients that cannot send headers (claude.ai connectors) is planned; see en/roadmap.md.

What an agent should know