Integrations

Reqvire integrations expose the same semantic engineering graph to coding assistants, CI jobs, GitHub workflows, and local tools. The goal is to keep model evidence close to the engineering work that changes it.

Integration Pages

MCP Server

Streamable HTTP MCP server, tool discovery, read/report tools, mutation mode, and semantic evidence.

Coding Assistants

Claude Code plugin, Codex skills, MCP workflows, assistant prompts, and AI-native Reqvire use cases.

Common Entry Points

CLI

Use reqvire validate, search, model, coverage, traces, submodels, ontologies, and serve in local or CI workflows.

MCP

Run reqvire mcp for Streamable HTTP tools that MCP-capable assistants can discover and call; npx is available as a no-install convenience.

Assistant packages

Install Claude Code plugins or Codex skills when the assistant environment supports native commands or skill files.

GitHub

Run validation, coverage, traces, and change-impact checks in pull requests or issue-comment workflows.

CI Example

curl -fsSL https://raw.githubusercontent.com/reqvire-org/reqvire/main/scripts/install.sh | bash
reqvire validate
reqvire coverage --json --output reports/coverage.json
reqvire traces --json --output reports/traces.json
reqvire change-impact --json --output reports/impact.json

Integration Guardrails

Run integrations from the repository root or pass --workspace explicitly.
Keep MCP mutation mode disabled unless the client is trusted to write model files.
Use JSON output for CI and assistant workflows that need stable machine-readable data.
Use ontology and collect outputs when the assistant needs semantic context before editing.