Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
mcp-integration - Skill - OpenSmartRoute
Skillv1.0.0
mcp-integration
Pattern for designing and validating MCP integrations with typed parameters, descriptive tools, and graceful failure handling.
Imported from ynotfins/AI-Project-Manager (tri-project-chatgpt-handoff/open--claw/open-claw/AI_Employee_knowledgebase/AI_employees/software-architect/skills/mcp-integration/SKILL.md). Install upstream with npx skills add ynotfins/AI-Project-Manager --skill mcp-integration. Copyright stays with the author.
MCP Integration
Status: READY
Purpose
Extend agent capabilities with MCP servers that are understandable, secure, and genuinely usable by agents.
Standards
Tool names must be descriptive verb_noun phrases.
Validate all inputs and return structured outputs.
Use environment variables for secrets only.
Keep tools stateless and single-purpose.
Test real tool-call loops, not just unit tests.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# 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}'
Installed into a catalogue, chosen by a router
Install mcp-integration 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.
