Menu

Shipping a remote MCP server with its own OAuth 2.1 server: notes from HireGPS
📰

Shipping a remote MCP server with its own OAuth 2.1 server: notes from HireGPS

DEV Community: fastapi·Volkan Şark·13 days ago
#vEXFbciU
#devtofastapi#devto#dev#client#server
Reading 0:00
15s threshold

I'm the founder of HireGPS , a tool that reads a CV against a target role the way a recruiter would and explains the risks behind the score. This autumn we shipped a remote MCP server so people can use it from Claude and other MCP clients. It lives at https://mcp.hiregps.app/mcp and is listed in the official MCP Registry as app.hiregps/hiregps .

Getting the tools to work took a few days. Getting authorization right took most of the project. These are the decisions that mattered, including one design we threw away.

The design we threw away: reusing the app's login

Our web app already signs users in through a hosted auth provider. The obvious plan was to make that provider the MCP authorization server and let MCP clients receive the same kind of token the web app uses.

We dropped it after testing what that token could do. A web session token is built for the user sitting in front of the app.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.