Integration Examples (API, MCP, Plugins)

This page shows practical integration patterns you can build around declarch. Core idea: keep declarch simple, extend behavior from outside.

Extension examples (external executables)

1) Security audit plugin

Command name example: declarch-ext-security-audit

Reads package inventory from:
- declarch info --list --format json --output-version v1
Checks vulnerability/advisory sources.
Outputs risk summary for CI.

2) Notification plugin

Command name example: declarch-ext-notify

Runs after sync in CI/local automation.
Sends concise report to Discord/Slack/Telegram.
Useful for shared infra/team setups.

3) Team policy plugin

Command name example: declarch-ext-policy-team

Rejects forbidden packages/backends before apply.
Enforces naming/module conventions.
Great for organization-wide baseline rules.

4) Export plugin

Command name example: declarch-ext-export

Converts declarch managed state/plan into other formats:
- CSV/JSON inventory
infra report artifacts
dashboard feed input

Protocol reference:

docs/contracts/v1/extensions-protocol.md

MCP examples (good first step)

Read-only MCP tools are low-risk and high value.

Candidate MCP tools:

declarch_info
declarch_lint
declarch_search
declarch_sync_dry_run

These can call declarch and parse machine output (v1 envelope).

API examples (optional)

If needed later, an API can mirror existing command surfaces:

GET /info
GET /lint
GET /search?q=...
POST /sync/dry-run

Keep API responses aligned with the same v1 envelope contract.

Integrations in CI/CD

PR validation:
- declarch lint --strict
- declarch --dry-run sync
Artifact export:
- store info/list machine output as CI artifacts.
Team notifications:
- send drift warnings or preview summaries.

Suggested rollout order

Stabilize machine output contracts (v1).
Build read-only MCP adapter externally.
Add extension discovery/runtime (declarch ext) incrementally.
Re-evaluate embedded API only when real usage needs it.