MCP Bootstrap
ontoskills can install ontomcp and wire it into supported MCP clients in one command.
Quickstart
# Global by defaultnpx ontoskills install mcp --claudenpx ontoskills install mcp --codex --cursor
# Project-local onlynpx ontoskills install mcp --cursor --vscode --projectScope model
--global: configure the current user or machine--project: configure only the current repository/workspace
If you omit both flags, ontoskills uses --global.
Supported clients
| Client | Global | Project | Bootstrap mode |
|---|---|---|---|
| Claude Code | Yes | Yes | Native CLI command |
| Codex | Yes | Manual | Native CLI command |
| Qwen Code | Yes | Yes | Native CLI or settings.json fallback |
| Cursor | Yes | Yes | JSON file |
| VS Code | Yes | Yes | CLI for global, JSON file for project |
| Windsurf | Yes | Manual | JSON file |
| Antigravity | Best effort | Manual | Config detection or manual fallback |
| OpenCode | Yes | Yes | JSON file |
What gets registered
Every client is configured against the same managed runtime:
~/.ontoskills/bin/ontomcpBy default ontomcp reads compiled ontologies from:
~/.ontoskills/ontologiesCommon commands
# Claude Code, globalontoskills install mcp --claude
# Claude Code + Codex + Cursor globallyontoskills install mcp --claude --codex --cursor
# Cursor and VS Code only for this repoontoskills install mcp --cursor --vscode --project
# Install runtime without touching any clientontoskills install mcpManual fallbacks
Some clients do not expose a stable project-local bootstrap flow. In those cases ontoskills:
- installs
ontomcp - tries the safest supported automation path
- prints exact manual steps if the client still needs user action
This is intentional: the command should never block MCP installation just because one client needs a manual final step.