Guides
14 guides for the act layer: building a remote MCP server, signing agents in with OAuth, shipping a CLI, adding WebMCP, exposing OpenAPI, getting listed, and testing the way an agent will. Every step is tied to a dated source and every guide shows what this directory measured.
| Guide | The job |
|---|---|
| Build and ship a remote MCP server on Cloudflare or Vercel | Get a Streamable HTTP server live with auth on either host, with the exact packages and commands. |
| OAuth for MCP servers: CIMD first, DCR for older clients | Implement the 2026-07-28 authorization flow end to end and know which registration methods clients will try. |
| Put a CLI on npm for agents and document it | Ship a CLI an agent can run without a browser, with machine output and an exit code CI can read, using Ora, Stripe and Vercel as worked cases. |
| Add WebMCP to a page | Register page tools through document.modelContext and know which browsers and agents will call them today. |
| MCP, A2A and WebMCP by job | Choose the surface by the job: tools on a server, delegation to another agent, or actions on a live page. |
| Get listed in each MCP registry | Publish once to the official registry and submit where review applies, with what each one checks. |
| Test your MCP server the way an agent will | Run the calls a client makes, in order, read-only, and record what came back. |
| What tool descriptions do to agent success | Write tool names, descriptions, schemas and annotations that agents select correctly and that reviewers accept. |
| Expose an OpenAPI file agents can find | Publish the OpenAPI file where agents follow links to it, and decide when to wrap it as MCP. |
| Keep an MCP server agent ready in CI | Fail the build when discovery, auth metadata or tool annotations regress. |
| Remote MCP auth patterns compared | Pick between an open server, an API key and OAuth with or without client registration, and see what each looks like to an agent and in this directory. |
| Publish an MCP server card | Describe an MCP server in a small JSON file that agents and scanners can read before they connect, using Ora's own cards as the worked example. |
| How many tools an MCP server should list | Choose a tool count by what the servers in this directory list, what scanners reward and what Ora's own two servers do. |
| Which MCP protocol versions and transports servers speak | See which protocol versions and transports the open MCP servers in this directory answered with, and which to support today. |