Integrations: MCP, A2A, and webhooks

Maps to: Integrations: MCP, A2A, webhooks.

Scope

Inbound discovery of your agent by external clients, outbound tool and data access, and event delivery when runs complete.

Design questions

• Which integration surfaces are first-class versus bespoke HTTP adapters.
• Versioning and auth for MCP and agent-to-agent endpoints.
• Webhook signing, allowlists, retries, and idempotent downstream consumers.
• Mapping external identities to internal tenancy and trace tags.

Tradeoffs

• Open protocols reduce adapter sprawl but require operational maturity.
• Webhooks simplify orchestration but shift reliability to receivers.
• Many MCP servers increase capability and supply-chain risk.

Evaluation hooks

• External MCP client invokes agent with same auth guarantees as first-party UI.
• Orchestrator agent calls worker across deployment boundary via agreed protocol.
• Webhook delivery on failure paths and success paths with retry policy.

Reference notes

See LangChain runtime article (integrations figure).