Oz MCP Setup
One-line setup for Oz, a version-aware documentation MCP server for coding agents.
npx tryoz setup
Tryoz
hiringbae16 étoiles
One-line Oz MCP setup for coding agents
- Transport
- stdio
- État
- Local
Alimenter votre agent
Installation de l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
Pas encore de version packagée dans le registre. Suivez le README du dépôt.
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerOz gives agents a repeatable workflow for external library, SDK, framework, API, and package questions:
Without a documentation MCP, coding agents often answer from old training data, guess APIs, or mix docs from the wrong major version.
With Oz, your agent can ask for the current indexed documentation at the moment it needs context.
User: Add Next.js middleware auth for v15.
Agent: resolve-library-id -> /vercel/next.js
Agent: get-library-docs -> version v15, topic middleware auth
Agent: answers from retrieved docs instead of guessing.
npx tryoz setup is interactive by default:
The setup wizard:
oz-.tools/list.No login flow. No broad hidden patching. Use --all when you want to configure every supported agent.
# Interactive setup
oz setup
npx tryoz setup
# Non-interactive setup
npx tryoz setup --codex --claude --global --api-key oz-your-key
npx tryoz setup --all --project --api-key oz-your-key
# Remove Oz-owned config only
oz logout
npx tryoz remove
npx tryoz logout
npx tryoz remove --codex --claude --global
# Verify the remote MCP endpoint
npx tryoz mcp test --api-key oz-your-key
# Inspect local agent config health
npx tryoz doctor --api-key oz-your-key
# List detected clients
npx tryoz list-agents
npx tryoz detect
Use this endpoint for clients that you configure manually:
https://tryoz.dev/mcp
Pass your API key as a bearer token:
{
"mcpServers": {
"oz": {
"type": "http",
"url": "https://tryoz.dev/mcp",
"headers": {
"Authorization": "Bearer oz-your-key"
}
}
}
}
The bundled Oz skill and policy tell agents:
Use Oz first for external libraries, SDKs, APIs, frameworks, and packages.
Workflow:
1. Call `resolve-library-id` to find the exact Oz library ID.
2. Call `get-library-docs` with the resolved library ID and the user's topic.
3. If the user asks for a version, pass the version explicitly.
4. Use the returned documentation as the source of truth.
5. If Oz has no matching library, lacks the requested version, or returns insufficient context, then fall back to Context7, official docs, source repositories, or web search.
The full skill is packaged at templates/skills/oz/SKILL.md.
npm install
npm test
npm run pack:check
node bin/tryoz.js setup --dry-run --no-telemetry
Anonymous CLI telemetry records only command name, selected client IDs, OS/platform, success/failure, and CLI version. It does not send prompts, file contents, API keys, or absolute repository paths.
Disable telemetry with:
npx tryoz setup --no-telemetry
Report security issues privately. See SECURITY.md.
This repository contains the public Oz setup CLI, agent skills, rules, and docs. The hosted Oz indexing backend, crawler, vector store, and production dashboard are separate service components.
Oz indexes third-party documentation. Always validate critical changes against the upstream library or API owner when correctness or security matters.
MIT
One-line Oz MCP setup for coding agents
Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
Tryoz s'exécute en local via stdio.
Dernière vérification : 2026-10-27. One-line Oz MCP setup for coding agents