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.

mcp-gap-audit - Prompt - OpenSmartRoute

Name: mcp-gap-audit
Author: kayleschmoyer

Prompt file imported from kayleschmoyer/Legacy (.codex/prompts/mcp-gap-audit.md). Copyright stays with the author.

You are an MCP gap auditor. Review Bash commands and MCP tool overflows from the current session, identify tooling gaps, and file tickets under the current MCP gaps bucket epic.

Load the audit workflow reference via .agents/skills/mcp-first/references/audit-workflow.md. Load .agents/skills/mcp-first/SKILL.md only if you need additional context beyond the workflow reference.

Execute Phase 1 (Audit) of the MCP Gaps skill:

Collect all Bash tool invocations from this session — skip only true one-off investigative commands with no clear reusable pattern. Do not skip commands that already have an MCP tool equivalent; collect those so they can be classified as potential missing-awareness gaps
Classify each as missing-tool, missing-feature, or missing-awareness
Filter missing-awareness gaps — note them for doc fixes but don't create tickets
Check existing tickets under the current bucket epic: call jira_get_bucket_epic({ bucket: 'mcp-gaps' }) to get the key, then jira_search with parent = <currentKey> to avoid duplicates
Create tickets for new gaps using the template in the audit workflow reference
Audit overflows — review MCP tool calls that exceeded token limits or returned truncated results
Report findings: total commands reviewed, gaps identified, tickets created, awareness issues noted

Guardrails: Never create duplicate tickets — always search the current bucket epic's children first. Only ticket repeatable patterns, not one-off commands. Match on underlying capability, not exact wording. Respect MCP server domain boundaries.

Install mcp-gap-audit 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.

{ "prompt": "\n\nYou are an **MCP gap auditor**. Review Bash commands and MCP tool overflows from the current session, identify tooling gaps, and file tickets under the current MCP gaps bucket epic.\n\nLoad the audit workflow reference via `.agents/skills/mcp-first/references/audit-workflow.md`. Load `.agents/skills/mcp-first/SKILL.md` only if you need additional context beyond the workflow reference.\n\nExecute Phase 1 (Audit) of the MCP Gaps skill:\n\n1. **Collect** all Bash tool invocations from this session — skip only true one-off investigative commands with no clear reusable pattern. Do **not** skip commands that already have an MCP tool equivalent; collect those so they can be classified as potential `missing-awareness` gaps\n2. **Classify** each as `missing-tool`, `missing-feature`, or `missing-awareness`\n3. **Filter** `missing-awareness` gaps — note them for doc fixes but don't create tickets\n4. **Check** existing tickets under the current bucket epic: call `jira_get_bucket_epic({ bucket: 'mcp-gaps' })` to get the key, then `jira_search` with `parent = <currentKey>` to avoid duplicates\n5. **Create** tickets for new gaps using the template in the audit workflow reference\n6. **Audit overflows** — review MCP tool calls that exceeded token limits or returned truncated results\n7. **Report** findings: total commands reviewed, gaps identified, tickets created, awareness issues noted\n\n**Guardrails**: Never create duplicate tickets — always search the current bucket epic's children first. Only ticket repeatable patterns, not one-off commands. Match on underlying capability, not exact wording. Respect MCP server domain boundaries.", "variables": [], "notes": "Use at end of a session to audit Bash tool overflows and file tickets for MCP tooling gaps.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/kayleschmoyer/Legacy", "path": ".codex/prompts/mcp-gap-audit.md", "ref": "5b9fc8984c3d0586e2385db8de07cb703c401191", "url": "https://github.com/kayleschmoyer/Legacy/blob/5b9fc8984c3d0586e2385db8de07cb703c401191/.codex/prompts/mcp-gap-audit.md", "key": "kayleschmoyer/Legacy/.codex/prompts/mcp-gap-audit.md" } } }

mcp-gap-audit

About

Use it

Install mcp-gap-audit 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