MCP API

Transport

Myria v1 exposes MCP over stdio only.

The server implements:

• initialize
• tools/list
• tools/call

Conversation Tools

myria.append_event

Appends one canonical event.

Key fields:

• timestamp
• channel
• participants
• payload
• optional source_event_key
• optional topic_hints
• optional internal

myria.query_event_nodes

Returns a rooted tree of raw event nodes.

Query fields:

• participants
• optional context_id
• optional query
• optional topic_hints
• optional include_internal
• optional limit

myria.query_references

Returns a rooted tree of summary/reference nodes plus event refs and, when needed, fresh events.

It uses the same query input shape as query_event_nodes.

Admin and Observability Tools

myria.get_event

Fetches one exact event by event_id.

myria.get_topic

Fetches one exact topic metadata record by topic_id.

myria.get_active_snapshot

Returns whether an active snapshot exists and, if so, the active snapshot metadata.

myria.list_snapshots

Lists snapshots in reverse chronological order.

myria.get_snapshot_status

Returns live builder and snapshot status, including:

• active snapshot
• latest snapshot
• unindexed tail size
• last received event time
• inactivity and threshold readiness
• whether a build is currently running
• last build trigger, timings, error, and output snapshot

myria.trigger_build

Starts a manual build when manual triggering is enabled by config.

Response Shape

MCP tool responses are structured JSON results wrapped in MCP tool content.

Read tools return one rooted multi-child tree.

Important response properties:

• snapshot_id
• root
• constraints
• degraded
• optional response metadata

Policy Split

Myria keeps conversation tools and admin/observability tools separate so callers can apply policy on top of the MCP surface.