read_page and discover, requires an AgentWeb account and aw_ API key; account creation runs in-conversation through the one-link sign-in flow. Check the returned status or verification before reporting completion.
Does it work on my site?
AgentWeb currently maps over 1,100 sites, each with named, executable actions. Calllist_actions for the live catalogue (paginated, with per-site action counts), or browse the mapped-site library. Passing an exact domain to list_actions returns that site’s full action definitions with parameters. If a site is not mapped yet, request_map queues a build and agentweb_map_status reports progress.
Two entry points
- Use AgentWeb: connect the MCP server and run mapped website actions for a user. Start with the quickstart.
- Install AgentWeb for a business: make a site or repo discoverable and callable by agents. Start with Install AgentWeb.
Start here
- AgentWeb quickstart
- MCP server and tool definitions
- Authentication and target-site connections
- Developer overview
- OpenAPI specification
- Public MCP tool manifest
- Full agent-readable reference
Execution sequence
- Authenticate with an
aw_API key (create one with the one-link sign-in tools). - Read a page or call discovery for the target domain, then list mapped actions.
- Connect the target-site account if the selected action requires it.
- Confirm the inputs and obtain approval for consequential actions.
- Execute once and use the structured result to report success, failure, or required intervention.