Overview

Complete technical specifications, standards, and quick references for the vCon MCP Server.

Overview

This reference section provides authoritative technical documentation for:

  • IETF vCon Specifications - Complete standard definitions

  • Database Schema - PostgreSQL table structures and relationships

  • MCP Protocol - Model Context Protocol integration details

  • API Standards - Tool, resource, and prompt specifications

  • Compliance Matrices - Regulatory framework mappings

  • Quick References - Fast lookup guides for common tasks


Essential References

🎯 Quick Start References

Document
Purpose
Time
Audience

Critical field corrections checklist

5 min

All developers

Terms and definitions

-

All users

Command-line tool usage

10 min

Developers

📋 Specification References

Document
Purpose
Time
Audience

Complete vCon specification

45 min

Implementers

Model Context Protocol details

30 min

Integrators

Full PostgreSQL schema (matches migrations)

25 min

DBAs, agents

IETF-oriented DDL narrative

20 min

DBAs

MCP search tools and behavior

15 min

Developers

🔧 Implementation References

Document
Purpose
Time
Audience

Known issues and fixes

15 min

Developers

Upgrading existing implementations

30 min

Migrators

Regulatory requirements mapping

20 min

Compliance teams

📚 Feature References

Document
Purpose
Time
Audience

Core functionality reference

30 min

All users

Proprietary capabilities

30 min

Enterprise customers

Extension system design

20 min

Plugin developers


By Use Case

🎯 "I'm implementing vCon for the first time"

  1. Start here: Quick Reference - Know what to avoid

  2. Read: IETF vCon Core - Understand the standard

  3. Reference: Agent database schema - Implement storage

  4. Verify: Implementation Corrections - Check for issues

🔄 "I'm migrating existing vCon code"

  1. Audit: Implementation Corrections - Identify issues

  2. Plan: Migration Guide - Follow migration steps

  3. Verify: Quick Reference - Confirm compliance

  4. Test: Testing Referencearrow-up-right - Run compliance tests

🔍 "I'm reviewing vCon code"

  1. Quick check: Quick Reference - Fast verification

  2. Deep check: Implementation Corrections - Known issues

  3. Schema check: Agent database schema - Database compliance

  4. Standards check: vCon Spec - Spec adherence

🛠️ "I'm integrating with MCP"

  1. Protocol: MCP Protocolarrow-up-right - Understanding MCP

  2. Tools: ../api/tools.md - Available tools

  3. Resources: ../api/resources.md - Resource URIs

  4. Prompts: ../api/prompts.md - Query templates

📊 "I need compliance documentation"

  1. Overview: Compliance Matrixarrow-up-right - All regulations

  2. GDPR: GDPR-specific mappings

  3. CCPA: CCPA-specific mappings

  4. HIPAA: HIPAA-specific mappings


Reference Categories

📖 Standards & Specifications

IETF vCon Standard

  • vCon Core Specification - Complete IETF draft reference

    • Main vCon object structure

    • Party, Dialog, Analysis, Attachment objects

    • Required vs optional fields

    • Encoding options

    • Extensions and must_support

  • vCon Data Typesarrow-up-right - Type definitions and validation

    • TypeScript interfaces

    • Zod schemas

    • Validation rules

    • Example objects

MCP Protocol

🗄️ Database & Storage

  • Agent database schema - Deployed PostgreSQL schema (authoritative for agents)

    • Core and operational tables, MVs, tenant columns, RLS summary

    • Pointers to migrations for RPC signatures

  • Corrected schema - IETF-oriented DDL (not the full catalog)

  • Search tools - MCP search tools

    • Keyword, semantic, hybrid, tags

  • Migrations under supabase/migrations/ - Source of truth for search_vcons_* SQL functions and index definitions

🔧 Implementation Guides

📋 Quick References

✅ Compliance & Standards

🎨 Feature References


Critical Corrections Summary

This implementation fixes 7 critical issues found in many vCon implementations:

  1. Analysis Schema Field - Uses schema not schema_version (Section 4.5.6)

  2. Analysis Vendor Requirement - vendor is required, not optional (Section 4.5.5)

  3. Analysis Body Type - body is string type, not object (Section 4.5.7)

  4. Party UUID Field - Added per spec Section 4.2.12

  5. Encoding Defaults - No default values, explicit only

  6. Dialog Type Constraints - Must be one of 4 valid types (Section 4.3.1)

  7. Dialog New Fields - Added session_id, application, message_id

See Quick Reference for detailed checklist.


Specification Sources

Primary Sources

  • IETF vCon Core: draft-ietf-vcon-vcon-core-02

    • Location: ../background_docs/draft-ietf-vcon-vcon-core-02.txt

    • Working Group: https://datatracker.ietf.org/wg/vcon/

  • IETF vCon Privacy Primer: draft-ietf-vcon-privacy-primer-00

    • Location: ../background_docs/draft-ietf-vcon-privacy-primer-00.txt

  • vCon Consent (Draft): draft-howe-vcon-consent-00

    • Location: ../background_docs/draft-howe-vcon-consent-00.txt

  • SCITT Architecture: draft-ietf-scitt-architecture-15

    • For transparency service integration

    • Location: ../background_docs/draft-ietf-scitt-architecture-15.txt

  • AI Preferences Vocabulary: draft-ietf-aipref-vocab-01

    • For AI-related metadata

    • Location: ../background_docs/draft-ietf-aipref-vocab-01.txt


Version Information

Current Version

  • Server Version: 1.2.0

  • vCon Spec Version: 0.4.0 (draft-ietf-vcon-vcon-core-02)

  • Schema Version: 1.2.0

  • Last Updated: April 2026

Version History

See Changelog for complete version history.

Compatibility

  • Node.js: 18.x or higher

  • PostgreSQL: 15.x or higher

  • Supabase: Latest stable

  • MCP SDK: 0.4.x


Contributing to Reference Docs

Reporting Issues

Found an error in the reference documentation?

  1. Check if it's already in Implementation Corrections

  2. Open an issue on GitHub with:

    • Document name and section

    • Expected vs actual content

    • IETF spec reference (if applicable)

Submitting Updates

To update reference documentation:

  1. Verify against IETF spec

  2. Update relevant markdown file

  3. Update cross-references

  4. Submit pull request with changes

See Contributing Guide for details.


Additional Resources

Documentation

  • IETF vCon Working Group: https://datatracker.ietf.org/wg/vcon/

  • MCP Protocol: https://modelcontextprotocol.io/

  • Supabase Docs: https://supabase.com/docs

  • pgvector: https://github.com/pgvector/pgvector

Community

  • GitHub: https://github.com/vcon-dev/vcon-mcp

  • Issues: Report bugs and request features

  • Discussions: Ask questions and share ideas


Quick Navigation

By Role

Developers: Quick ReferencevCon SpecAgent database schemaAPI Docsarrow-up-right

DBAs: Agent database schemaSearch toolsPerformance Tuningarrow-up-right

Integrators: MCP Protocolarrow-up-rightAPI ReferenceIntegration Guidearrow-up-right

Compliance Teams: Compliance Matrixarrow-up-rightGDPRarrow-up-rightCCPAarrow-up-right

By Task

Setting up: Quick StartAgent database schemaTestingarrow-up-right

Migrating: Implementation CorrectionsMigration GuideTestingarrow-up-right

Extending: Plugin Architecturearrow-up-rightCustom Toolsarrow-up-rightAPI Referencearrow-up-right

Troubleshooting: Error Referencearrow-up-rightFAQarrow-up-rightGitHub Issuesarrow-up-right


Need help? Check the FAQarrow-up-right or ask in GitHub Discussionsarrow-up-right.

Found an issue? Report it in GitHub Issuesarrow-up-right with the documentation label.


Reference documentation is the authoritative source for implementation details. When in doubt, consult the IETF specifications.

Last updated