vcon-mcp

Run AI analysis (sentiment, summary, topics) on a specific vCon by UUID. Useful for re-analyzing or analyzing vCons that were created before the AI sidecar was available.

Get AI analyzer status: sidecar connection, analysis count, model info.

Ask a natural language question about conversations. Provide context chunks from vCon transcripts for RAG-style Q&A.

Get the full JSON-LD-ex semantic enrichment for a vCon, including provenance annotations, confidence scores, integrity hash, and agent capabilities.

Verify the cryptographic integrity of a vCon enrichment. Returns whether the document has been tampered with since signing.

Query confidence scores for a vCon. Returns per-party and per-analysis confidence with Subjective Logic opinions. Supports temporal decay calculation.

Trace the full provenance chain for a vCon: who created it, what models analyzed it, confidence scores, integrity verification, and data lineage.

Compute trust propagation through an analysis chain using Subjective Logic. For example: transcript confidence → sentiment confidence → summary confidence.

Run a read-only Cypher query against the vCon knowledge graph. Use for finding repeat callers, topic clusters, contact networks, and escalation patterns.

Get pre-built graph insights: repeat_callers, topic_clusters, escalation_paths, contact_network, or graph_stats.

Manually trigger ingestion of a SIPREC XML or JSON file from the watch folder. Useful for testing or re-processing.

Get SIPREC adapter status: watch folder path, pending files, processed count.

Import a Teams call record JSON file and create a vCon. File must follow MS Graph callRecord schema.

Import all Teams call record JSON files from a folder. Defaults to the sample-data directory.

Get Teams adapter status: watch folder, stats, connection info.

Import a WhatsApp exported chat .txt file and create a vCon.

Import all WhatsApp .txt files from a folder. Defaults to sample-data directory.

Parse a WhatsApp chat export and return a preview without creating a vCon.

Get WhatsApp adapter status.

Get vCon schema definition in the requested format (json_schema or typescript).

Get example vCons (minimal, phone_call, chat, email, video, full_featured) as JSON or YAML.

Retrieve tags from a vCon. Provide a specific key to get one tag value, or omit key to get all tags as an object.

Remove all tags from a vCon.

Search for vCons that have specific tag values. All specified tags must match (AND logic). REQUIRED: You must provide the tags parameter as an object with at least one key-value pair.

Create a new vCon from a predefined template (phone_call, chat_conversation, email_thread, video_meeting, custom).

Add a dialog (conversation segment) to an existing vCon. Dialog can be a recording, text, transfer, or incomplete.

Add an attachment to an existing vCon. Attachments can be files, documents, or other data related to the conversation.

Delete a vCon and all its related data (parties, dialog, analysis, attachments). This operation cannot be undone.

Update top-level vCon metadata (subject, extensions, must_support). For dialog, analysis, attachments use their specific tools.

Replace the dialog at the given index (PUT semantics: omitted fields are cleared). Index is the dialog's position in the vCon's dialog array.

Remove the dialog at the given index. Per IETF core-02 §4.1.8 the slot is preserved as a content-stripped placeholder (keeps "type") so positional references in analysis/attachments do not shift.

Replace the analysis at the given index (PUT semantics: omitted fields are cleared). vendor is REQUIRED per IETF spec.

Remove the analysis at the given index. Analysis is a referential leaf, so the element is hard-deleted and the remaining analyses are renumbered to stay contiguous.

Replace the attachment at the given index (PUT semantics: omitted fields are cleared).

Remove the attachment at the given index. Attachments are referential leaves, so the element is hard-deleted and the rest renumbered to stay contiguous. Note: removing a "tags" attachment clears the vCon's tags.

Append a party to an existing vCon. Returns the new party index.

Replace the party at the given index (PUT semantics: omitted fields are cleared).

Remove the party at the given index. Per IETF core-02 §4.1.8 the slot is preserved as an empty placeholder Party Object so positional references (dialog.parties, attachment.party, etc.) do not shift. Set anonymize=true to write {name:"anonymous"} instead of an empty object.