Skip to content

feat: integrate external Conduit MCP service - #8

Draft
devXyi wants to merge 6 commits into
mainfrom
feat/conduit-integration
Draft

feat: integrate external Conduit MCP service#8
devXyi wants to merge 6 commits into
mainfrom
feat/conduit-integration

Conversation

@devXyi

@devXyi devXyi commented Aug 12, 2026

Copy link
Copy Markdown
Owner

What this does

  • Adds a standalone Prexus-side Go client for the external devXyi/conduit-mcp service.
  • Uses Conduit's documented Auth0 client-credentials flow and Streamable HTTP MCP session.
  • Adds a guarded /conduit/tools endpoint for read-only integration verification.
  • Adds a dedicated conduit:read RBAC permission.
  • Keeps Meteorium/risk routing unchanged for safety.

Architecture

Prexus consumes Conduit as an external MCP service; Conduit is not copied into or owned by Prexus.

Safety

No existing risk endpoint, Supabase path, JWT auth path, or Meteorium routing is changed by this branch. The Conduit integration remains inactive until CONDUIT_CLIENT_ID and CONDUIT_CLIENT_SECRET are configured.

Note

Render environment entries for Conduit are intentionally not applied automatically in this branch because the current Render service naming in render.yaml does not match the live service naming and should not be changed blindly.

Copilot AI lite review requested due to automatic review settings August 12, 2026 17:34

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

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.

2 participants