Request the Review Desk
← All posts

· Auth & access

How remote MCP servers authenticate

A remote MCP server is a door to tools and possibly to data, so it needs a lock. Since March 2025 the standard lock has been OAuth — the same family of controls your IT team already uses for everything else.

The authorization spec

MCP added an authorization specification on March 26, 2025, built on OAuth 2.1 with PKCE, and refined it in the protocol's June 18, 2025 release. Rather than invent a new scheme, the maintainers piggybacked on OAuth because most organizations already run an identity provider. In MCP terms the server acts as the protected resource server, an identity provider is the authorization server, and the client (Claude Desktop) is the OAuth client.

What that looks like in practice

Why this matters for a firm

Authentication is what makes a remote tool safe to put in front of a team. Because access is tied to identity, a firm can give the right people the review tools, revoke access when someone leaves, and keep that control inside the OAuth practices IT already maintains. AECdesign.ai is an authenticated remote server — the access model is a feature, not an afterthought.

Sources

Draft, not determination. Every substantive AECdesign.ai result is a draft. A licensed engineer of record must review, revise, accept, or reject each finding before it is issued. AECdesign.ai never provides a sealed determination.

An authenticated review tool inside Claude Desktop.

Request the managed Review Desk or self-serve platform access; we quote the right path in writing before billing.