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.

context-mcp - Skill - OpenSmartRoute

Name: context-mcp
Author: vinilana

Imported from vinilana/context-engineering-material-aula (context-mcp/AGENTS.md). Install upstream with npx skills add vinilana/context-engineering-material-aula --skill context-mcp. Copyright stays with the author.

Project Instructions

Language

Write all project content in English, including documentation, source comments, public errors, examples, tests, commits, and release notes.

Architecture

Define domain actions as capabilities with explicit input, output, access, and execution contracts.
Keep the generated direct, MCP HTTP entry points on the single engine.invoke path.
Keep models, prompts, providers, data stores, and tools behind replaceable engine-owned dependencies.
Use defineConnector for provider- or technology-specific outbound integrations and inject only their engine-owned ports into capabilities.
Keep connector configuration and clients at the composition root; connector construction performs no external I/O.
Keep business logic out of src/direct.ts, src/mcp-http.ts.
Do not add framework-wide registries, service locators, or adapter-specific business logic.
Keep HTTP authentication fail-closed until src/http-auth.ts verifies a real credential.

Delivery

Follow RED, GREEN, REFACTOR for executable behavior.
Run npm run check before completing a change.
Keep CLAUDE.md as a symbolic link to this file so agent instructions have one source of truth.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install context-mcp 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.

{ "ocm": "1", "id": "vinilana-context-engineering-material-aula-context-mcp", "kind": "skill", "name": "context-mcp", "description": "Write all project content in English, including documentation, source comments, public errors, examples, tests, commits, and release notes.", "publisher": "vinilana", "version": "1.0.0", "capabilities": { "domains": [ "coding", "customer_support" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Write all project content in English, including documentation, source comments, public errors, examples, tests, commits, and release notes." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/vinilana/context-engineering-material-aula", "path": "context-mcp/AGENTS.md", "ref": "aeb8bc49aa18d8dba470ee2fdf27b69367b3e136", "url": "https://github.com/vinilana/context-engineering-material-aula/blob/aeb8bc49aa18d8dba470ee2fdf27b69367b3e136/context-mcp/AGENTS.md", "key": "vinilana/context-engineering-material-aula/context-mcp/AGENTS.md" } }, "instructions": "# Project Instructions\n\n## Language\n\nWrite all project content in English, including documentation, source comments,\npublic errors, examples, tests, commits, and release notes.\n\n## Architecture\n\n- Define domain actions as capabilities with explicit input, output, access, and execution contracts.\n- Keep the generated direct, MCP HTTP entry points on the single `engine.invoke` path.\n- Keep models, prompts, providers, data stores, and tools behind replaceable engine-owned dependencies.\n- Use `defineConnector` for provider- or technology-specific outbound integrations and inject only their engine-", "cost": { "context_tokens": 304 } }

context-mcp

About

Project Instructions

Language

Architecture

Delivery

Use it

Install context-mcp 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