Context
The MCP connector catalog (packages/trueforge/catalog/mcp-catalog.yaml) already lists Confluence, Jira, Linear, and Notion, each configured against TrueFoundry-hosted/shared MCP endpoints (mcp.atlassian.com, mcp.linear.app, mcp.notion.com) using DCR (OAuth Dynamic Client Registration).
Raised during triage of #490: for these connectors, TrueForge (this repo) is the layer being used underneath — it's the shared API/OAuth app going through TrueFoundry's proxy. A user may instead want to connect their own instance/property for a given workspace (e.g. their own self-hosted Confluence, their own Notion/Linear OAuth app or workspace), rather than always going through the shared TrueFoundry-hosted MCP server.
Ask
Scope out what "bring your own connector" would look like for DCR-based catalog entries — e.g.:
- Per-tenant/per-property override of the MCP server URL and/or OAuth client used for a catalog connector (instead of only the shared
mcp.*.com endpoint hardcoded in the catalog).
- Whether this reuses the existing "Add MCP Server" custom-connector flow (
AddMcpServerForm.tsx) or needs a distinct "use my own account" option surfaced alongside the catalog's "Connect" button for connectors that today only offer the shared DCR entry.
This is a scoping/design issue, not an implementation ticket yet — no code changes proposed here.
Context
The MCP connector catalog (
packages/trueforge/catalog/mcp-catalog.yaml) already lists Confluence, Jira, Linear, and Notion, each configured against TrueFoundry-hosted/shared MCP endpoints (mcp.atlassian.com,mcp.linear.app,mcp.notion.com) using DCR (OAuth Dynamic Client Registration).Raised during triage of #490: for these connectors, TrueForge (this repo) is the layer being used underneath — it's the shared API/OAuth app going through TrueFoundry's proxy. A user may instead want to connect their own instance/property for a given workspace (e.g. their own self-hosted Confluence, their own Notion/Linear OAuth app or workspace), rather than always going through the shared TrueFoundry-hosted MCP server.
Ask
Scope out what "bring your own connector" would look like for DCR-based catalog entries — e.g.:
mcp.*.comendpoint hardcoded in the catalog).AddMcpServerForm.tsx) or needs a distinct "use my own account" option surfaced alongside the catalog's "Connect" button for connectors that today only offer the shared DCR entry.This is a scoping/design issue, not an implementation ticket yet — no code changes proposed here.