The on-ramp for the IETF vCon standard into the agent layer. One install gives Claude the vCon MCP server, the spec-compliance rule set, and commands to validate, inspect, and create vCons.
/plugin marketplace add vcon-dev/vcon-plugin
/plugin install vcon@vcon-dev
The plugin runs vcon-mcp against your own
conserver deployment. Set these in your environment before starting Claude Code:
| Variable | Required | What |
|---|---|---|
VCON_SUPABASE_URL |
yes | Your deployment's Supabase URL |
VCON_SUPABASE_ANON_KEY |
yes | Anon key for that deployment |
VCON_TOOLS_PROFILE |
no | readonly (default) or full |
The server itself needs no install. The plugin runs it with npx -y vcon-mcp, which
fetches it on first use.
Bearer-token auth against a conserver endpoint is the supported path for now. Other auth schemes are out of scope.
- Skill
vcon-compliance— audits a repo against draft-ietf-vcon-vcon-core-02 and the extension drafts. Carries the non-negotiables so you never regenerate the usual bugs (schema_version, missingvendor, unprefixedcontent_hash). /vcon-validate— structure, field names, content hash format, signature./vcon-inspect— readable dump of parties, dialog, analysis, attachments./vcon-create— a compliant vCon from a template.
Every command reports whether a vCon carries a lawful-basis attachment. None of them will invent one.
Session capture (Claude Code sessions written out as vCons), then a governance skill per extension draft as each revision is submitted: identity-binding, lawful-basis, provenance, and a DSAR command from the privacy primer.
Apache-2.0, copyright VCONIC.