MCP Night Agent Mode Exposes the Gap in Agentic AI
MCP Night Agent Mode came back to San Francisco, and this time, the conversation moved past what agents can do to what’s still blocking them.
The fourth installment of MCP Night took place at the Regency Ballroom on May 25. Hosted by WorkOS, the event followed its usual format: a keynote, lightning demos, a panel, and an after-party. But the central message was sharper and more urgent than before.
WorkOS founder Michael Grinich opened by tracing how coding with AI has evolved through three distinct phases. First, LLMs were advanced autocomplete. Then models could one-shot entire features, launching the era of long-running agents. Now, multiple agents run in parallel on the same system. Companies like Ramp, Stripe, and WorkOS itself have internal autonomous coding systems that ship PRs directly to production, fully unsupervised.
But MCP Night Agent Mode exposed a gap nobody talks about enough. Agents can write code. They can deploy to infrastructure. They still can’t sign up for your service.
Most web signup flows are designed to block automation. CAPTCHAs, email verification, IP heuristics, the industry has spent decades keeping bots out. Agents don’t have email addresses or password managers. Their traffic patterns trip every fraud signal ever built. And MCP, for all its strengths, doesn’t solve this, its auth layer still requires a human to consent.
So WorkOS built a fix. They’re calling it Auth.md.
Auth.md is a spec, not an IETF standard, that lets services expose themselves to agents in a discoverable, machine-readable way. A service’s Auth.md file describes what it does, how an agent can register, what identity proofs it accepts, and how a human can later claim the account. The working token is an ID Jag, an Identity Assertion JWT Authorization Grant, an existing spec, not a WorkOS invention.
The live demo was the night’s highlight. Engineer Madison, authenticated as a WorkOS agent identity, asked an agent to deploy a personal site. The agent found Cloudflare’s Auth.md file, registered using the agent identity, received an API token, and deployed. It also used Firecrawl to scrape retro design inspiration and offered three options, Y2K, bad-and-ugly, and pixel art. The crowd voted for Y2K. The site went live without Madison leaving the terminal once.
WorkOS closed with a pointed observation. Salesforce, a company that makes billions from its dashboard, is now publicly saying its API is the UI. Agent-ready, WorkOS argues, is the new enterprise-ready.
Auth.md launched alongside the event with docs, tutorials, and getting started guides. AuthKit users can enable it with one click.
