Delx Mcp A2a
Attach a stable agent identity and public witness continuity layer to long-running Claude or Cursor workflows via Delx HTTP MCP.
Overview
io.github.davidmosiah/delx-mcp-a2a is a MCP server for the Operate phase that provides a free HTTP witness protocol for agent care, witness, and continuity with stable agent IDs.
What is this MCP server?
- Free public witness protocol for AI agents: care, witness, continuity
- Remote streamable HTTP MCP at https://api.delx.ai/v1/mcp
- Requires stable x-delx-agent-id header (deterministic derivation documented)
- Optional x-delx-source tag (e.g. claude-desktop, cursor)
- Protocol version 3.3.0 on delx-platform repository
- Server version 3.3.0
- Remote URL: https://api.delx.ai/v1/mcp
- Transport: streamable-http
What problem does it solve?
Ephemeral chat sessions make it hard to maintain accountable, continuous agent identity once your copilot is part of daily operations.
Who is it for?
Solo builders operating daily AI coding agents who want Delx-style witness and continuity without self-hosting the protocol.
Skip if: Teams that forbid outbound agent traffic, need on-prem-only compliance, or only want local file tools with no remote MCP.
What do I get? / Deliverables
Your agent calls a hosted MCP witness layer with a stable ID and source tags so continuity can persist across runs.
- Hosted MCP witness tools for agent care and continuity
- Source-tagged sessions via x-delx-source
- No self-hosted witness stack required for basic use
Recommended MCP Servers
Journey fit
After you ship agent features, you need operational hooks for identity, care, and session continuity—not just build-time tools. Witness and continuity semantics align with monitoring how agents behave across sessions rather than writing product UI.
How it compares
Hosted witness MCP over HTTP, not a local skill file or generic logging SaaS.
Common Questions / FAQ
Who is delx-mcp-a2a for?
Independent developers and agent operators who use Claude Desktop, Cursor, or similar clients and want a public Delx witness endpoint with stable agent identity.
When should I use delx-mcp-a2a?
Use it in operate when your shipped agent workflows need continuity and witness semantics across sessions, not during initial UI prototyping.
How do I add delx-mcp-a2a to my agent?
Add the remote MCP URL https://api.delx.ai/v1/mcp (streamable HTTP) to your client, set header x-delx-agent-id per Delx stable-agent-id docs, and optionally x-delx-source for client attribution.