REST serves the developers building against your API. MCP serves the agents now trying to use it. Most teams treat these as competing standards and have to pick one.

They’re not rivals, they’re layers: most MCP servers just call REST internally to do the real work. The best ones don’t convert every endpoint into a tool, they design around what the agent’s trying to accomplish.

Shipping that server also means shipping OAuth 2.1 with scoped tokens. WorkOS AuthKit already speaks that spec, so you skip building an auth provider on top.

Read the breakdown →

My thanks to WorkOS for sponsoring last week at DF to promote their MCP server. Debugging SSO, managing users, adjusting auth policies, configuring branding: every configuration task has lived behind a UI that only a human can drive.

The WorkOS MCP server gives agents the same access as your dashboard login. Hundreds of operations, discoverable at runtime. Connect in one command via OAuth, with scoped tokens instead of a master API key. Pass a screenshot of your marketing site and ask your agent to match the login page. If a human had to do it before, an agent can do it now. Connect your agent today.

Debugging SSO, managing users, adjusting auth policies, configuring branding: every configuration task has lived behind a UI that only a human can drive.

The WorkOS MCP server gives agents the same access as your dashboard login. Hundreds of operations, discoverable at runtime. Connect in one command via OAuth, with scoped tokens instead of a master API key. Pass a screenshot of your marketing site and ask your agent to match the login page. If a human had to do it before, an agent can do it now.

Connect your agent →

My thanks, once again, to WorkOS for sponsoring DF last week. Users expect apps and agents to reach the tools they already work in. Every integration that gets you there is a different OAuth flow, a different token lifecycle, and weeks of infrastructure before you write a line of product code.

WorkOS Pipes handles it with one API call. Pre-built connectors for GitHub, Slack, Salesforce, Google Drive, and more. Pipes handles OAuth, token refresh, and credential storage. You call the real provider API with a fresh token, every time.

Connect to 100+ providers with WorkOS Pipes.

Users expect apps and agents to reach the tools they already work in. Every integration that gets you there is a different OAuth flow, a different token lifecycle, weeks of infrastructure before you write a line of product code.

WorkOS Pipes handles it with one API call. Pre-built connectors for GitHub, Slack, Salesforce, Google Drive, and more. Pipes handles OAuth, token refresh, and credential storage. You call the real provider API with a fresh token, every time.

Connect to 100+ providers →

My thanks to WorkOS for sponsoring DF last week to promote Auth.md, their new open protocol for AI agent registration. (Who’d have thunk that I’d be getting paid to promote new uses for Markdown 22 years after releasing it?)

Sign-up forms were built for humans in browsers, so how do AI agents programmatically register with services? That’s the question Auth.md aims to answer. It’s a single Markdown file you host at your domain that tells agents how to register your users, which flows you support, what scopes you expose, and how credentials get issued. It’s like robots.txt but for agent registration.

Cloudflare, Firecrawl, and Resend have already adopted it.

An open protocol authored by WorkOS. Read the spec.

When an AI agent tries to complete a task that requires a new account, it hits a wall: the sign-up form. There’s no standard for how an agent registers a user with an app on their behalf.

auth.md is a file you host at your domain that tells agents how to register your users, which flows you support, what scopes you expose, and how credentials get issued. Think robots.txt, but for agent registration. It composes existing OAuth standards.

Cloudflare, Firecrawl, and Resend have already adopted it.

An open protocol authored by WorkOS. Read the spec.

My thanks to WorkOS for sponsoring DF last week to promote Auth.md, their new open protocol for AI agent registration.

Sign-up forms were built for humans in browsers, so how do AI agents programmatically register with services? That’s the question Auth.md aims to answer. By exposing a single, machine-readable Markdown file at your service root, AI agents can dynamically discover your OAuth Protected Resource Metadata, parse required scopes, and authenticate seamlessly.

Markdown, baby. Who’d have thunk it?

With native support in WorkOS AuthKit, you can now implement this protocol out of the box, giving AI tools a standardized, secure way to log into your application. Read the Auth.md docs, and watch its on-stage introduction at the MCP Night: Agent Night keynote.