Claude, Cursor and anything else speaking the Model Context Protocol can authenticate to your MCP server — with a token AuthOwl issues for that server and no other.
Authorization server metadata is published where the Model Context Protocol requires it, so a client resolves your endpoints on its own.
Register each MCP server and tokens are bound to it. One minted for your server cannot be spent at another, or at anyone else’s.
Access tokens expire quickly and can be revoked, because nobody is watching the window in which a leaked one still works.
$ curl -s https://mcp.yourapp.com/mcp 401 Unauthorized WWW-Authenticate: Bearer resource_metadata="…" → agent discovers AuthOwl, then asks for a token resource=https://mcp.yourapp.com/mcp ✓ aud is your server. Nowhere else accepts it.
Included on every plan - Free through Scale.
Register your MCP server, and every token issued for it stops working anywhere else.