Skip to content

feat(burn): expose native MCP with personal tokens - #29

Draft
aviyashchin wants to merge 2 commits into
mainfrom
codex/21-native-mcp-hosting
Draft

aviyashchin wants to merge 2 commits into
mainfrom
codex/21-native-mcp-hosting

Conversation

@aviyashchin

@aviyashchin aviyashchin commented Sep 18, 2026

Copy link
Copy Markdown

Outcome

Expose the existing native Onyx MCP server through Burn's API proxy. Each request uses a personal token and native Onyx permissions. Reuses the pinned backend image and FastMCP. No custom OAuth broker or application rewrite.

Adds one bounded Compose service and nginx routes for /mcp and /mcp/. The frontend strips the trailing slash, so both forms are required. Disables query-bearing INFO logs and extra file logging for the service. Updates the Auth0 gateway canary to expect the now-live canonical callback.

Tracks #21 (shared identity and native per-user access). Keeps #21 open for authenticated tool calls, cross-user denial and monitoring proof.

Validation

  • Independent source and deployment review: PASS after correcting slash routing, query logging, rollback cleanup and bind-mounted nginx configuration activation.
  • Native pinned-image health and token rejection, SSM 795f8e36-b07e-4e8b-a9c3-73f15945858d: {"native_health":"pass","missing_token":"denied","invalid_token":"denied"}.
  • Deployed reviewed hosting files, SSM 796e7fdc-e5f1-4f43-90c8-f9d96aea8f75, exit 0:
PASS: both MCP gateway paths reject absent and invalid personal tokens
Native MCP service started; gateway config valid; backups: 1789772117
  • Native gateway health 200 and nginx config check passed. API/background were not restarted for this MCP deployment.
  • git diff --check and Python compile check passed.
  • Earlier deployment returned 403 through stale gateway configuration and automatically restored the original files. Recreating only the gateway resolved the single-file bind-mount update.

Remaining acceptance

A user PAT must complete initialize, tools/list and a useful tool call. Public API-path access is blocked by this agent's network/browser policy, so loopback gateway proof is not public end-to-end proof. The user credential handoff is pending. Keep this draft until live positive acceptance and required CI are complete.

@vercel

vercel Bot commented Sep 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
onyx-executive Ready Ready Preview Sep 18, 2026 11:21pm UTC

@aviyashchin aviyashchin changed the title Expose native Burn MCP with personal-user authentication feat(burn): expose native MCP with personal tokens Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant