# Changelog All notable changes to the vCon MCP Server will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). ## \[Unreleased] *** ## \[1.2.0] - 2026-04-15 ### Added * REST API parity with MCP tool surface — full HTTP/JSON access at `/api/v1` (PR #46) * Predictable vCon contract tools: `vcon_fetch`, `vcon_search`, `vcon_capabilities`, `vcon_taxonomy`, `describe_response_shape` * HTTP transport (`MCP_TRANSPORT=http`) with Streamable HTTP and SSE * API-key authentication for REST and MCP HTTP endpoints (`API_KEYS`, `API_KEY_HEADER`, `API_AUTH_REQUIRED`) * Tool profiles and category controls (`MCP_TOOLS_PROFILE`, `MCP_ENABLED_CATEGORIES`, `MCP_DISABLED_CATEGORIES`, `MCP_DISABLED_TOOLS`) * Docker image published to `public.ecr.aws/r4g1k2s3/vcon-dev/vcon-mcp` with `main-`, `latest`, and semver tags * Build provenance exposed via `X-Version`, `X-Git-Commit`, `X-Build-Time` response headers * Pino structured JSON logging (stderr); OpenTelemetry instrumentation with OTLP exporter option * DNS rebinding protection options for HTTP transport (`MCP_HTTP_DNS_PROTECTION`, allowed hosts/origins) * Discovery surfaces and internal knowledge graph ### Changed * Tool catalog grew from 30 to 35 (5 new contract tools) * vCon version handling relaxed to accept any string or missing value * Dialog disposition validation relaxed to accept any string * Bearer token extraction tolerates leading whitespace in headers ### Fixed * Upsert vCon on duplicate UUID submission instead of erroring * Correct body serialization/deserialization for analysis and attachments (CON-352) * `getTags` no longer crashes on non-array attachment bodies *** ## \[1.0.1] - 2025-12 (approximate) > Date precise to the month only — the npm-published 1.0.1 pre-dated the current main lineage and its exact release date isn't in this repo. ### Added * Comprehensive database documentation for LLMs (architecture, quickstart, schema visual) * Row Level Security (RLS) support for multi-tenant isolation * Enhanced database status and analytics scripts * S3 sync functionality and backfill scripts * Tenant debugging support * Versioned resource URIs (vcon://v1/...) * Backup and restore functionality * Enhanced embedding generation with backfill options * Improved database inspection tools ### Changed * Updated package dependencies * Enhanced embedding scripts with continuous and backfill modes * Improved database status reporting with time-ago formatting * Enhanced dialog, attachment, and analysis type distribution logging ### Fixed * Removed obsolete test scripts and temporary files * Improved environment variable management in scripts *** ## \[1.0.0] - 2025-10-14 ### Added #### Core Features * Full CRUD operations for vCons (create, read, update, delete) * Component management (parties, dialog, attachments, analysis) * Advanced search capabilities (metadata, content, semantic, hybrid) * Tag management system with key-value pairs * Template-based vCon creation * Batch operations (import, export, bulk updates) * Validation and data quality checks * MCP resources for URI-based access * MCP prompts for query templates * Plugin system for extensibility #### Search & Query * Metadata search with filters (subject, party, date range) * Full-text content search with PostgreSQL trigrams * Semantic search with vector embeddings (pgvector) * Hybrid search combining keyword and semantic * Tag-based search and filtering * Aggregation and statistics #### Database * Normalized PostgreSQL schema for vCons * Full IETF spec compliance (draft-ietf-vcon-vcon-core-00) * Materialized views for tag queries * HNSW indexes for vector search * GIN indexes for full-text search * Foreign key constraints and referential integrity #### Developer Features * TypeScript with full type safety * Zod schemas for validation * Comprehensive test suite (Vitest) * Plugin development framework * Example plugins and code * MCP Inspector compatibility #### Documentation * Complete user guides * API reference documentation * Developer guides (architecture, testing, plugins) * IETF vCon specification reference * Database schema documentation * Migration guides and quick references ### Fixed #### Specification Compliance * ✅ Analysis uses `schema` not `schema_version` (Section 4.5.6) * ✅ Analysis `vendor` is required, not optional (Section 4.5.5) * ✅ Analysis `body` is string type, not object (Section 4.5.7) * ✅ Party object includes `uuid` field (Section 4.2.12) * ✅ Party object includes `did` field (Section 4.2.6) * ✅ Dialog includes `session_id`, `application`, `message_id` fields * ✅ No default values for `encoding` fields * ✅ Dialog `type` has proper CHECK constraint * ✅ vCon includes `extensions` and `must_support` arrays ### Technical Details #### Dependencies * `@modelcontextprotocol/sdk` ^0.4.0 * `@supabase/supabase-js` ^2.39.0 * `zod` ^3.22.4 * `typescript` ^5.3.3 * `vitest` ^1.2.0 #### Requirements * Node.js 18.x or higher * PostgreSQL 15.x or higher * Supabase (local or cloud) #### Database Schema Version * Version: 1.0.0 * vCon spec compliance: 0.3.0 (draft-ietf-vcon-vcon-core-00) *** ## \[0.9.0] - 2025-10-07 (Beta) ### Added * Initial beta release * Basic CRUD operations * Search functionality * Tag system implementation * Database schema design ### Known Issues * Documentation incomplete * Some edge cases in search not handled * Performance optimization needed *** ## Development Timeline ### Phase 1: Core Implementation (Completed) * ✅ Database schema with spec corrections * ✅ CRUD operations with validation * ✅ Basic search functionality * ✅ Tag management system * ✅ MCP protocol integration ### Phase 2: Advanced Features (Completed) * ✅ Semantic search with embeddings * ✅ Hybrid search * ✅ Plugin system * ✅ Batch operations * ✅ Template system ### Phase 3: Documentation (Completed) * ✅ User guides * ✅ API documentation * ✅ Developer guides * ✅ Reference documentation * ✅ VitePress site ### Phase 4: Production & Distribution (Completed in 1.2.0) * ✅ REST API parity with MCP surface * ✅ HTTP transport with API-key auth * ✅ Docker image pipeline to ECR * ✅ Pino structured logging + OpenTelemetry * ✅ Multi-tenant RLS ### Phase 5: Predictability & Discovery (Completed in 1.2.0) * ✅ Contract tools: `vcon_fetch`, `vcon_search`, `vcon_capabilities`, `vcon_taxonomy`, `describe_response_shape` * ✅ Discovery surfaces and internal knowledge graph ### Phase 6: Future Work (Planned) * ⏳ Privacy Suite plugin (consent, redaction, PII detection) * ⏳ Compliance tooling hooks (GDPR, CCPA, HIPAA) * ⏳ Performance hardening on large corpora *** ## Migration Guides ### Migrating to 1.0.0 If you're upgrading from a pre-1.0 version or another vCon implementation: 1. **Read the Migration Guide:** [MIGRATION\_GUIDE.md](/reference/migration_guide.md) 2. **Check Field Names:** [QUICK\_REFERENCE.md](/reference/quick_reference.md) 3. **Update Database:** [CORRECTED\_SCHEMA.md](/reference/corrected_schema.md) 4. **Run Tests:** Ensure compliance tests pass **Critical Changes:** * Analysis uses `schema` not `schema_version` * Analysis `vendor` is now required * Analysis `body` is string, not object * Party includes `uuid` field * Dialog includes new fields (`session_id`, `application`, `message_id`) *** ## Version Numbering We follow [Semantic Versioning](https://semver.org/): * **Major (X.0.0)**: Breaking changes, incompatible API changes * **Minor (0.X.0)**: New features, backward compatible * **Patch (0.0.X)**: Bug fixes, backward compatible ### What Triggers Version Bumps **Major (Breaking):** * Database schema changes requiring migration * API changes incompatible with previous versions * Required configuration changes **Minor (Features):** * New tools, resources, or prompts * New optional features * Performance improvements * Documentation enhancements **Patch (Fixes):** * Bug fixes * Security patches * Documentation corrections * Performance optimizations without API changes *** ## Release Notes ### v1.0.0 Release Highlights This first major release represents a production-ready, fully spec-compliant vCon MCP Server with: * **100% IETF Spec Compliance** - All known specification issues corrected * **Production-Ready Database** - Normalized schema with proper constraints and indexes * **Advanced Search** - Keyword, semantic, and hybrid search capabilities * **Extensible Architecture** - Plugin system for custom functionality * **Complete Documentation** - User guides, API reference, developer guides * **Professional Quality** - TypeScript, comprehensive tests, proper error handling **Perfect for:** * Production conversation data management * AI-powered conversation intelligence * Compliance and archival systems * Development and research **Not Included (Proprietary):** * Privacy Suite (consent management, PII detection) * Compliance tools (GDPR, CCPA, HIPAA automation) * Enterprise support *** ## Future Roadmap The roadmap below reflects work not yet started or in early planning. Concrete shipped versions live in the dated entries above. ### Near-term (post-1.2.0) * Privacy Suite plugin (consent management, PII detection, redaction) * Compliance tooling hooks (GDPR, CCPA, HIPAA support patterns) * Performance hardening on large corpora (cold-start full-text search) ### Longer-term * Cloud-native deployment patterns and horizontal scaling guidance * Additional storage backends *** ## Contributing See [CONTRIBUTING.md](/development/contributing.md) for how to contribute to this project. *** ## License ### Open Source Core The vCon MCP Server is released under the MIT License. ### Proprietary Features Privacy Suite and enterprise features are available under commercial license. *** ## Support * **Documentation:** * **Issues:** * **Discussions:** * **IETF Working Group:** *** **Note:** This changelog reflects the development history. Earlier versions (pre-1.0) were development/beta releases not intended for production use. *** *Last Updated: May 18, 2026* --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://mcp.conserver.io/reference/changelog.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.