Tech
MCP on OAuth 2.1: one URL and a consent click, no API key
Adding my tracker to Claude takes one URL and one click on a consent screen. Nobody makes a key, copies it, or pastes it anywhere.
The constraint: an MCP client that a person uses every day should not hold a long-lived secret the person had to handle by hand, and the person should be able to see and cut off what it can reach.
I'm Panth, and I lead the software team at Oizom. This is from ticket-tracker , my open-source board. Its decisions page lists the choices that are expensive to reve...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to