Skip to content

MCP Bootstrap

ontoskills can install ontomcp and wire it into supported MCP clients in one command.

Quickstart

Terminal window
# Global by default
npx ontoskills install mcp --claude
npx ontoskills install mcp --codex --cursor
# Project-local only
npx ontoskills install mcp --cursor --vscode --project

Scope 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

ClientGlobalProjectBootstrap mode
Claude CodeYesYesNative CLI command
CodexYesManualNative CLI command
Qwen CodeYesYesNative CLI or settings.json fallback
CursorYesYesJSON file
VS CodeYesYesCLI for global, JSON file for project
WindsurfYesManualJSON file
AntigravityBest effortManualConfig detection or manual fallback
OpenCodeYesYesJSON file

What gets registered

Every client is configured against the same managed runtime:

~/.ontoskills/bin/ontomcp

By default ontomcp reads compiled ontologies from:

~/.ontoskills/ontologies

Common commands

Terminal window
# Claude Code, global
ontoskills install mcp --claude
# Claude Code + Codex + Cursor globally
ontoskills install mcp --claude --codex --cursor
# Cursor and VS Code only for this repo
ontoskills install mcp --cursor --vscode --project
# Install runtime without touching any client
ontoskills install mcp

Manual fallbacks

Some clients do not expose a stable project-local bootstrap flow. In those cases ontoskills:

  1. installs ontomcp
  2. tries the safest supported automation path
  3. 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.