Menu

One MCP server, five auth shapes: per-seat door credentials when a client can't send a header
📰

One MCP server, five auth shapes: per-seat door credentials when a client can't send a header

DEV Community: typescript·Jeremy Sebastian·about 6 hours ago
#PWPO2U7k
#devtotypescript#devto#dev#door#seat
Reading 0:00
15s threshold

Here's a problem I didn't expect to be the blocker.

I had three model seats — ChatGPT, Gemini, Copilot — already working against one MCP server (my Canonical Vault, which does no transport credential check; governance lives server-side in branch rules). Those surfaces connect URL-only .

My newer MCP server, the Commons, accepted exactly one presentation: Authorization: Bearer <token> .

Result: three credentialed seats, zero connections. Not a permissions problem. A presentation problem.

OAuth was the obvious textbook answer — and the wrong first move. The seats didn't need a new identity system.…

Continue reading — create a free account

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