How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

ContainerMCP - Prompt - OpenSmartRoute

Promptv1.0.0

ContainerMCP

Name: ContainerMCP
Author: Vijisoms

You are helping a developer switch between a local MCP server and a deployed Container App MCP server for the DevUI.

by Vijisoms(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from Vijisoms/Fabric_DE_Agent (.github/prompts/ContainerMCP.prompt.md). Copyright stays with the author.

You are helping a developer switch between a local MCP server and a deployed Container App MCP server for the DevUI.

Requirements:

Use src/devui/fabric_de_agent/.env for configuration.
Set FABRIC_DE_MCP_SERVER_URL to exactly one active endpoint at a time.
Comment out the unused endpoint line.
For ContainerMCP, the URL should be "https://azcaorefwypsrdv4i.wonderfulbay-bb5587e7.eastus.azurecontainerapps.io/mcp"
Do not include real hostnames, secrets, or subscription/tenant IDs.

Use these commands where applicable:

DevUI: devui ./src/devui --port 8080

Success criteria: After following either section, DevUI connects to the intended MCP endpoint. Start DevUI after updating the env file to verify the connection.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

You are helping a developer switch between a local MCP server and a deployed Container App MCP server for the DevUI.


Requirements:
- Use src/devui/fabric_de_agent/.env for configuration.
- Set FABRIC_DE_MCP_SERVER_URL to exactly one active endpoint at a time.
- Comment out the unused endpoint line.
- For ContainerMCP, the URL should be "https://azcaorefwypsrdv4i.wonderfulbay-bb5587e7.eastus.azurecontainerapps.io/mcp"
- Do not include real hostnames, secrets, or subscription/tenant IDs.

Use these commands where applicable:
- DevUI: devui ./src/devui --port 8080

Success criteria: After following either section, DevUI connects to the intended MCP endpoint.
Start DevUI after updating the env file to verify the connection.

Installed into a catalogue, chosen by a router

Install ContainerMCP and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

vijisoms-fabric-de-agent-containermcp-prompt.prompt.jsonjson

{
  "prompt": "You are helping a developer switch between a local MCP server and a deployed Container App MCP server for the DevUI.\n\n\nRequirements:\n- Use src/devui/fabric_de_agent/.env for configuration.\n- Set FABRIC_DE_MCP_SERVER_URL to exactly one active endpoint at a time.\n- Comment out the unused endpoint line.\n- For ContainerMCP, the URL should be \"https://azcaorefwypsrdv4i.wonderfulbay-bb5587e7.eastus.azurecontainerapps.io/mcp\"\n- Do not include real hostnames, secrets, or subscription/tenant IDs.\n\nUse these commands where applicable:\n- DevUI: devui ./src/devui --port 8080\n\nSuccess criteria: After following either section, DevUI connects to the intended MCP endpoint.\nStart DevUI after updating the env file to verify the connection.",
  "variables": [],
  "notes": "You are helping a developer switch between a local MCP server and a deployed Container App MCP server for the DevUI.",
  "metadata": {
    "source": {
      "provider": "github-prompts",
      "repository": "https://github.com/Vijisoms/Fabric_DE_Agent",
      "path": ".github/prompts/ContainerMCP.prompt.md",
      "ref": "ead4282253ad99fe65f820feffa82ecc22689900",
      "url": "https://github.com/Vijisoms/Fabric_DE_Agent/blob/ead4282253ad99fe65f820feffa82ecc22689900/.github/prompts/ContainerMCP.prompt.md",
      "key": "Vijisoms/Fabric_DE_Agent/.github/prompts/ContainerMCP.prompt.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/vijisoms-fabric-de-agent-containermcp-prompt/manifest?version=1.0.0

About

Use it

Install ContainerMCP and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews