{
  "markdown": "# actionlayer\n\n<!-- mcp-name: io.actionlayer/actionlayer -->\n\nMCP server for [ActionLayer](https://actionlayer.io) — the concierge for Claude Code (and any MCP host) that takes action in the physical world on your behalf: book, order, register, resolve.\n\n> Previously published as `actionlayer-mcp`. That project is no longer\n> maintained and stopped at 0.6.0 — install `actionlayer` instead.\n\n## Install\n\nGet an API key from your ActionLayer dashboard at https://actionlayer.io, then:\n\n```bash\nclaude mcp add --scope user actionlayer \"uvx\" \"actionlayer\" \\\n  --env ACTIONLAYER_API_KEY=\"ak_…\" \\\n  --env ACTIONLAYER_API_URL=\"https://api.actionlayer.io\"\n```\n\nRestart Claude Code and ask it to do something for you.\n\n## Usage from other MCP hosts\n\n```bash\nactionlayer\n```\n\nWorks with Cursor, Cody, Codex, etc.\n\nEnv vars:\n- `ACTIONLAYER_API_KEY` — required\n- `ACTIONLAYER_API_URL` — defaults to `https://api.actionlayer.io`\n\n## Changelog\n\n### 0.7.1\n\nMetadata-only. Repositions the listing copy — ActionLayer is a\nconcierge that takes action in the physical world, not just a\nbrowser driver — and drops the repository URL from the published\nmetadata.\n\n### 0.7.0\n\nRenamed: published as `actionlayer` on PyPI from this release on\n(`actionlayer-mcp` is orphaned and frozen at 0.6.0). No code changes.\nThe command is now `actionlayer`; `actionlayer-mcp` remains as an\nalias. Includes everything from the unreleased 0.6.1.\n\n### 0.6.1\n\nNo code changes. Embeds the MCP Registry `mcp-name` ownership token\nso the package can be listed at registry.modelcontextprotocol.io.\n\n### 0.4.2\n\nInternal taxonomy scrub. No behavior change; tool descriptions and\n`next_action.prompt` fallbacks rephrased so calling agents don't\nsurface ActionLayer's internal terminology in their own user-facing\ntext.\n\n### 0.4.1\n\nPayment-card approval flow (Phase 2 of the agent payments plan).\n\n- `actionlayer_reply` now accepts `payment_approved: bool` for\n  tickets whose info_request includes `payment_status`. Users\n  approve a charge against their card-on-file with one call.\n- `actionlayer_get_task` / `actionlayer_next_action` surface\n  `card_brand`, `card_last4`, `amount_usd`, and `payment_status`\n  on the info_request payload so an agent can prompt the user\n  with \"Approve $X.XX charge on your <brand> card ending <last4>?\"\n- The card PAN itself NEVER crosses the MCP boundary. The charge\n  is completed against the user's card on file; the PAN never\n  appears on agent-visible surfaces. This is by design per\n  `docs/agent_payments_plan.md`.\n\n### 0.4.0\n\n**Backwards-incompatible — public API taxonomy changed.**\n\n- Ticket `state` collapses the in-flight phases into a single\n  public value `pending`. Polling code that branched on the\n  individual sub-phases (e.g. `if state == \"executing\"`) must\n  switch to `state == \"pending\"`. Terminal states (`completed`,\n  `failed`, `cancelled`) and `blocked_on_user` are unchanged.\n- `live_view_url` is no longer returned by the public tools\n  (`actionlayer_invoke_action`, `actionlayer_get_action_ticket`).\n  User-facing callers should drive the task via polling\n  `actionlayer_get_action_ticket` and responding to\n  `blocked_on_user` prompts.\n- `actionlayer_invoke_action` sync response now uses\n  `outcome=\"queued\"` (instead of `outcome=\"blocked\"`) when the\n  task is taking longer than the sync window allows. Callers\n  handling `outcome` need to add a `queued` branch: poll\n  `actionlayer_get_action_ticket` for terminal state.\n- Terminal tickets now carry a free-text `reason` field summarising\n  the outcome (derived from `result.summary` on completed, `error`\n  on failed). Pre-existing `result` / `error` fields preserved\n  for callers that want the raw structured payload.\n\n### 0.3.1\n- Update default API URL to `https://api.actionlayer.io`\n  (`api.action-layer.dev` still redirects, but the new host is the\n  current canonical name).\n\n### 0.3.0\n- Browser-only catalog. Per-session credential intake.\n\n### 0.2.0\n- Async-by-default dispatch for browser actions + ticket polling tool.\n\n### 0.1.0\n- Initial release.\n\n## License\n\nMIT",
  "bytes": 4052,
  "sha": "84b6e5e293e38c700ce6d09d31254a746000487c039f293e76d534bd5f84803e",
  "repo_slug": "",
  "fonte": "pypi",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_actionlayer_actionlayer_e7470bb2/readme"
}