REQ-FUN-053

MCP server authenticates via same bearer-token mechanism as REST

ID: REQ-FUN-053
Category: Functional Requirements
Status: approved
Priority: P0
Created: 2026-05-10T18:00:22.017Z
Approved: 2026-05-10T18:02:50.756Z
Updated: 2026-05-10T18:02:50.756Z

What

The MCP server SHALL authenticate via the same bearer-token mechanism as REST.

Acceptance

Same token works on both surfaces.

Source

OBJ-6.

established project management guidelines Mapping

Primary Knowledge Area: Integration Management
Secondary KA: Resource Management
Primary Process Group: Executing
established project management guidelines Deliverable: Project Management Plan

Shared bearer-token mechanism unifies actor identity across REST and MCP.