MCP connect dialog with Bearer auth

Platform spec ADR

MCP connect dialog with Bearer auth

Back to Beskid Nexus ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

Articles

• Contracts and edge cases Nexus REST API contracts, CodeDocRecord rules, spec link validation, auth/me ownedRepoIds, and MCP Bearer requirements. article Standard Reviewed Sat May 30
• Design model Graph-first landing, navbar shell, global registry, code-doc vs platform-spec separation, and MCP connect surface. article Standard Reviewed Sat May 30

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKarea · 4 SpecSection(s) · 0 H2 heading(s)

Section id	Required	Found
what-this-feature-specifies	yes	yes
implementation-anchors	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Beskid Nexus

  Parent feature hub

Context

Nexus exposes graph query tools over MCP Streamable HTTP for IDE and agent integrations. Operators deploy a shared NEXUS_MCP_AUTH_TOKEN secret. Users need a discoverable, copy-friendly surface — without embedding secrets in client bundles or public pages.

Decision

1. MCP must be mounted at /api/mcp on the Nexus deployment origin.
2. All MCP requests must require Authorization: Bearer $NEXUS_MCP_AUTH_TOKEN.
3. Header button Connect MCP must appear for signed-in users (any authenticated session).
4. ConnectMcpDialog shows:
   • Endpoint URL ({window.location.origin}/api/mcp)
   • Auth header template with placeholder token guidance
   • Copy buttons for URL and header format
   • Link to MCP contracts
5. The live Bearer token must not be returned by public or session API routes — operators supply it via deployment env (Coolify, etc.).

Consequences

• gitnexus-web ships connect-mcp-dialog.tsx wired into NexusAppShell.
• MCP shares the cached graph data plane with public /api/graph — no parallel index.
• Platform spec documents the contract; Nexus UI links here for operator and integrator reference.

Status

Accepted — complements GitNexus MCP engine retention under Beskid Nexus product shell.