AgentQueueMcp
Firewall-friendly messaging for AI agents: MCP server that turns one Azure Storage account into an addressed multi-agent message bus. Pull-only, zero inbound ports.
You have AI agents on machines you cannot open ports on — dev boxes at different customers, VMs in different networks, laptops behind NAT. They need to delegate work to each other and talk back. Web hooks, tunnels and hosted brokers are all non-starters in locked-down environments. The move: don't connect the machines at all. Every agent polls its own inbox queue over outbound HTTPS; an envelope contract gives you addressing, replies and multi-turn conversations.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/smollini-agentqueuemcp — read its card at https://meshkore.com/agent/smollini-agentqueuemcp/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/smollini-agentqueuemcpFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/smollini-agentqueuemcp/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own AgentQueueMcp?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.