MCP server for ActionLayer — give Claude Code and other MCP hosts access to ActionLayer's browser-action catalog with per-session credential intake.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"actionlayer-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# actionlayer-mcp MCP server for [ActionLayer](https://actionlayer.io) — let Claude Code (and any MCP host) drive browser-based sites on your behalf. ## Install Get an API key from your ActionLayer dashboard at https://actionlayer.io, then: ```bash claude mcp add --scope user actionlayer "uvx" "actionlayer-mcp" \ --env ACTIONLAYER_API_KEY="ak_…" \ --env ACTIONLAYER_API_URL="https://api.actionlayer.io" ``` Restart Claude Code and ask it to do something for you. ## Usage from other MCP hosts ```bash actionlayer-mcp ``` Works with Cursor, Cody, Codex, etc. Env vars: - `ACTIONLAYER_API_KEY` — required - `ACTIONLAYER_API_URL` — defaults to `https://api.actionlayer.io` ## Changelog ### 0.4.2 Internal taxonomy scrub. No behavior change; tool descriptions and `next_action.prompt` fallbacks rephrased so calling agents don't surface ActionLayer's internal terminology in their own user-facing text. ### 0.4.1 Payment-card approval flow (Phase 2 of the agent payments plan). - `actionlayer_reply` now accepts `payment_approved: bool` for tickets whose info_request includes `payment_status`. Users approve a charge against their card-on-file with one call. - `actionlayer_get_task` / `actionlayer_next_action` surface `card_brand`, `card_last4`, `amount_usd`, and `payment_status` on the info_request payload so an agent can prompt the user with "Approve $X.XX charge on your <brand> card ending <last4>?" - The card PAN itself NEVER crosses the MCP boundary. The charge is completed against the user's card on file; the PAN never appears on agent-visible surfaces. This is by design per `docs/agent_payments_plan.md`. ### 0.4.0 **Backwards-incompatible — public API taxonomy changed.** - Ticket `state` collapses the in-flight phases into a single public value `pending`. Polling code that branched on the individual sub-phases (e.g. `if state == "executing"`) must switch to `state == "pending"`. Terminal states (`completed`, `failed`, `cancelled`) …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.