

You can now control access to individual MCP servers using resource indicators. When an MCP client requests a token, AuthKit scopes it to the specific MCP server the client asked for, so a token issued for one server can't be used with another. This gives you cleaner access boundaries across multiple MCP servers running under the same AuthKit environment. See the MCP integration guide to set it up.