Creative Agent should support A2A protocol (no agent-card at /.well-known/agent.json)

[bokelley]

Summary

The Creative Agent at https://creative.adcontextprotocol.org doesn't expose an A2A agent card at the standard /.well-known/agent.json endpoint, preventing A2A protocol usage.

Current Behavior

• MCP Protocol: ✅ Working - agent responds to MCP tool calls
• A2A Protocol: ❌ No agent-card - discovery fails

Testing shows the A2A status as "No agent-card" while MCP operations work correctly.

Expected Behavior

For full protocol compatibility, the Creative Agent should:

1. Serve an A2A agent card at /.well-known/agent.json
2. Support A2A JSON-RPC protocol alongside MCP

Impact

• Buying agents that only support A2A cannot interact with the Creative Agent
• Limits interoperability in multi-agent workflows
• Inconsistent with other AdCP reference agents which support both protocols

Questions

1. Is A2A support intentionally omitted from the Creative Agent?
2. If so, should this be documented as an MCP-only agent?
3. If not, what's needed to add A2A support?

Reference

The Test Agent and Wonderstruck both support both MCP and A2A protocols. The Creative Agent is the only reference agent that appears MCP-only.

🤖 Generated with Claude Code