src/routes/proxy/routes/unified.ts — the main route handlersrc/routes/proxy/adapters/unified-translation.ts — the translation layer/v1/unified/chat/completions endpoint receives a standard OpenAI format request. It reads the model field, looks it up in the existing model registry to find which provider owns it (anthropic, openai, gemini, groq, cohere etc.), then delegates to that provider's existing adapter. The response is translated back to OpenAI format before sending to the client.oaiToAnthropic, oaiToGemini, oaiToCohere) and a NativeWrapperStreamAdapter that handles streaming for translated providers.GET /v1/unified/models — queries the existing model registry and returns all models from all providers in standard OpenAI list format. This is needed so n8n can discover available models.handleLLMProxy pipeline — virtual GET /v1/unified/modelsPOST /v1/unified/chat/completionsPOST /v1/unified/:agentId/chat/completionsRead-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!
Organizarion scope connection badgeOrganizarionOrganization block addedOrganization block
How "Organization" chip should it look like when MCP has both org-wide and personal installation?
Also Organization icon on the scope card is not matching the icon on the MCP Server card. Do we really need it?
Should we really split "Shared connections" here on teams and "organization"
InternalMCPCatalog.tsx, items are split into two sections based on scope: (item) => item.scope === "personal",
);
const publishedItems = allFilteredItems.filter(
(item) => item.scope !== "personal",
);```
These render under headings `Unpublished` and `Published`. The problem is that this implies a lifecycle — a personal connection looks like a draft waiting to be promoted. In reality `scope === "personal"` is a permanent access boundary, not a transient state. A user could reasonably ask "how do I publish this?" and there's no answer.
Would it be ok to rename these to reflect what the distinction actually is (access scope)?
`draftItems` → `personalItems`,
`publishedItems` → `sharedItems`,
headings:
`Unpublished` → `Personal`
`Published` → `Shared`
Pure rename, no behavior change. Also, that would be similar to *Connections* tab wordings.
The code was added here <https://github.com/archestra-ai/archestra/pull/3180/changes#diff-dda8f6bec4ed047f79cc8f7b815b10028c5a3e3f3c09e6d1bc63e436ae2e6e8eR968> by <@U0975SLALTT>