Start with the core protocols

The agent ecosystem is becoming a stack of protocols rather than one platform. MCP connects agents to tools and context. WebMCP brings structured actions into the browser. A2A handles agent-to-agent communication. Commerce protocols handle cart and payment authority.

An authority site should explain how these pieces fit instead of treating every announcement as a disconnected trend.

Use resources by job to be done

If you are connecting tools, start with MCP. If you are preparing a website for browser agents, study WebMCP and accessibility. If you are preparing product pages for buying agents, study UCP, ACP, and checkout data.

If you are installing workflows inside an open-source harness, start with AGENTS.md-style instructions, folder structure, and approval gates.

Keep the directory alive

Agent protocols are moving quickly. A useful resource directory should include last-updated dates, source links, and notes about whether a protocol is a stable standard, proposal, preview, or platform-specific implementation.

ClawCurrent should revisit this directory monthly and turn important changes into separate how-to posts.

FAQ

What should a beginner read first?

Start with MCP basics, then AGENTS.md install files, then WebMCP and agentic commerce once you understand tool execution and approval gates.

Should ClawCurrent cover closed-source agents too?

Yes, when they affect open-source harness users. The editorial center should remain open-source harnesses and portable agent workflows.

Sources and further reading

Model Context Protocol specificationChrome WebMCP documentationChrome Lighthouse llms.txt documentationGoogle Universal Commerce Protocol announcementOpenAI Instant Checkout and ACP

Ready to see the full catalog?

Browse all 42 agent-ready business kits. Each includes pre-configured agent roles, prompts, workflows, install steps, and approval gates.

Shop all business kits