Temporary image generation instructions
Image 1 – icon / symbol: Create a detailed cartoon icon or symbolic illustration for AxiOwl article 62, "How AxiOwl Uses MCP Metadata to Identify the Replying Session". Show an owl-themed AI message dispatcher, named agent badges, and a clear visual metaphor for this topic: MCP metadata is how AxiOwl can know which session is calling back. Style: modern SaaS cartoon, bold shapes, high contrast, polished but friendly, simple or transparent background, no readable text.
Image 2 – article image / screenshot: Create a blog hero image or product-style screenshot for AxiOwl article 62, "How AxiOwl Uses MCP Metadata to Identify the Replying Session". Show a developer workstation or clean software interface where named AI agents exchange messages through AxiOwl. Include visual cues specific to this topic: MCP metadata is how AxiOwl can know which session is calling back. Style: polished SaaS website image, widescreen 16:9, believable fictional UI, no real credentials or real private data.
MCP metadata is how AxiOwl can know which session is calling back.
When a provider replies through an AxiOwl MCP tool, the content of the reply is not enough. The provider can say "I am Codebase review," but display text can be wrong, duplicated, stale, or invented. AxiOwl needs provider-owned identity whenever possible.
That is the role of metadata.
Useful metadata can include the provider brand, provider surface, session id, thread id, cwd, host, or other stable session information. AxiOwl maps that information to registry rows so the reply can be attributed to the correct target.
This is especially important for CLI providers. An environment variable or user-supplied name is weaker than metadata produced by the provider runtime or a robust provider patch. Final support should prefer provider-owned identity because it prevents false attribution.
MCP metadata also improves debugging. If a reply comes from an old session, the metadata can reveal that. If two windows have similar names, metadata can distinguish them. If a provider has stale config, metadata can show that the expected surface did not call back.
The user-facing result is simple: AxiOwl can say who replied with more confidence.
Without metadata, AxiOwl has to rely on names and context. With metadata, it can connect the reply to a provider session in the registry.
For multi-agent work, sender identity is not optional polish. It is part of the trust model.