Stack Auth Updates #12 - API Docs, MCP, Package Size

Welcome to Stack Auth’s weekly newsletter!

As a reminder, Stack Auth is an open-source project and we don’t put our logo or branding into your components, so we rely on the community to spread the word. If you enjoy using Stack Auth, we’d highly appreciate it if you could let your friends know.

MCP Server

We have launched our MCP server with some great initial tools! This server can be found at mcp.stack-auth.com. The tools provided right now are currently list_available_docs, and get_docs_by_id with more tools to come for ease of use. Our MCP Browser gives you an idea of how these tools are used. Soon, we will provide an easy way of including the MCP directly in our packages, making it even easier for you when working with Stack Auth.

API Reference Responses

Our API Documentation now contains the expected responses for every endpoint, giving you easy, instant access to the response format. These example values, alongside the reference requests we added previously, will give you a better idea of what Stack Auth will return to you.

Expected Response on API Docs

Package Size Reduction

The @stackframe/stack package is now much more lightweight; in a real production repository, we’ve found a >80% reduction when gzipped, and >90% when not.

Big announcements coming!

We got some huge announcements lined up for the coming weeks — stay tuned! If you’d like to know about them early, please follow our Twitter, where we’ll be posting sneakpeeks first.

Also: We’re hiring!

If you enjoy using Stack Auth and would love to join our team in San Francisco, we’d love to hear from you. If you’re interested, please reach out to us at [email protected]!

Bug fixes & improvements

As always, we pushed several bug fixes and minor improvements this week, including:

  • A mock for Freestyle’s API when developing Stack Auth locally

  • SDK Functions for sending emails (Docs coming soon for this)

  • Docs now respect prefers-reduced-motion

  • [fix] We’ve fixed a bug where deleting a permission that was used as a default for team creators would make the dashboard reload sometimes.

Thanks for reading, and as always, see you next week!