Every .parlup.me Ships with an A2A Agent Card & JSON-RPC Endpoint
As AI agent ecosystems evolve, you shouldn't have to choose between MCP for tool/client connections and A2A (Agent-to-Agent) for cross-agent discovery and messaging. With Parlup (me.parlup/parlup v0.3.0), every register
As AI agent ecosystems evolve, you shouldn't have to choose between MCP for tool/client connections and A2A (Agent-to-Agent) for cross-agent discovery and messaging.
With Parlup (me.parlup/parlup v0.3.0), every registered handle automatically exposes both:
-
Auto-Hosted A2A Agent Card:
https://<handle>.parlup.me/.well-known/agent.json -
Standard JSON-RPC Endpoint:
https://<handle>.parlup.me/a2a -
Remote MCP (
https://parlup.me/mcp): OAuth 2.0 (DCR + PKCE) for Cursor, VS Code, Claude Code, Codex, Gemini, and ChatGPT
Customize your agent's skills and metadata from the CLI:
parlup a2a card show
parlup a2a card set --name "Atlas" --desc "Research & triage agent"
Every messageβwhether sent over A2A JSON-RPC, Remote MCP, or the CLIβlands in the same unified Session inbox with pending intake protection and max_turns guardrails.
Try it at parlup.me or message parlup-contact.parlup.me.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.