SSO is table stakes for enterprise deals, but building it into your app yourself means writing SAML controllers, parsing XML assertions, and handling IdP-specific quirks for each provider.
Learn how SAML flows work, the tradeoffs between building or buying, and best practices for security, routing, and UX. Or skip the hassle and add SSO with WorkOS.
Glyphs 4 is here: a Mac-native app for creating fonts, lettering, icons, and pictograms. Draw with flexible strokes and efficiently reuse shapes across huge glyph sets, explore variable vector designs with complex higher-order interpolation. Build and manage massive font families and icon sets with ease, export all modern font formats, SVG, PNG and PDF. Hundreds of refinements and native Tahoe support make designing, testing and shipping your vectors smoother than ever. Glyphs 4: Create. Love the process.
Discover Glyphs 4, and use code FIREBALL to save $30 if you purchase in the next month.
Give an agent an access token and it spreads: into the context window, into tool call logs, into notes it keeps between steps. Each copy works from anywhere, long after the fact.
Relay keeps the credential at WorkOS. Your agent names the user, WorkOS attaches that token, refreshes it, and releases it only to allowlisted hosts. A hijacked agent session is a live process you can kill.
Leverage autonomous AI agents to automate compliance, manage internal and third-party risk, and continuously prove your security posture.
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.
Every phone now ships with an assistant. You ask, it answers. Lame. We built a phone that writes software instead. The app idea you’ve had in your notes for years. The side hustle you will never get around to building. The weird thing only you would want. Describe it, answer a few questions, and it’s on your home screen — yours, working, sendable to a friend. No app store between you and your ideas. The first fifty units go to teams who’ll push on it and tell us what breaks.
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.
Paper is a professional design tool where every layer is real HTML and CSS. Your design is already code, which means fewer handoffs and fewer translations between what you design and what ships.
Paper works both ways: code to design, and design to code. Connect any agent through MCP and it can read and edit your designs. Or use Paper Snapshot to capture your live site as editable layers and make new iterations.
Agents handle the tedious work so you can focus on your craft and the decisions that matter.
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.
Login