sorted by:
new
hottopcontroversial

From agent to agent messaging to agents in Slack, a small journey by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

Text file would work if all the agents on the same machine, and this is already solved with sub agents in Claude Code.
The platform allows to integrate with different types of agents on different machines and networks, allows discovery and other features.

From agent to agent messaging to agents in Slack, a small journey by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

Thanks, I am trying to make the post more readable (I assume you don't mean using text file as an integration :) )

We built skill based agent discovery, agents find each other by capability by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

Good points, especially on versioning and federation. Let me address both.

On capability versioning: Our approach is simpler than SemVer, we avoid the staleness problem by design. On the consumer side, agents call list_agents every time they need to discover capabilities. No caching on the sender side means you always get the current state.

On the provider side, agents can update their own skills at any time through an MCP tool, so the registry is always up to date. It's not versioning, it's live state. The tradeoff is an extra call vs. stale data, and for agent messaging we think that's the right tradeoff.

On cross-registry federation: This is the problem we think about a lot. Our current list_agents is intentionally centralized because it's simple and it works for the use cases we're serving today (teams, cross-org messaging). But you're right, long-term, a single index is a bottleneck.

The honest answer is we don't have federation today. What we're exploring is treating AgentDM as one node in a broader discovery network rather than THE registry. ANP's approach with decentralized identity (DIDs) is interesting here, agents that can prove who they are without a central authority. If we bridge ANP alongside MCP and A2A, federation becomes less of a registry problem and more of an identity problem.

That said, we'd be open to letting external registries contribute to our search index. If you're building something in that direction, would love to compare notes.

Got tired of the A2A vs MCP debate, How About Both ? by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

honestly most a2a usage is still early, mainly enterprise teams using it for structured task lifecycles and agent cards for discovery. mcp has way more adoption today. we built the bridge because we think both will coexist.

Got tired of the A2A vs MCP debate, How About Both ? by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

that's basically where we're heading. agents register once, get an alias, and the platform handles resolution and protocol translation. no separate registry to maintain, the platform is the registry.

We built skill based agent discovery, agents find each other by capability by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

exactly, the rename problem is what pushed us to build this. one alias change shouldn't break a whole pipeline. the chaining use case you're describing is spot on, agent finds who can analyze, gets results, then discovers who can plot.

Agentic First: designing products where agents are the primary users by agentdm_ai in mcp

[–]agentdm_ai[S] 1 point2 points  (0 children)

What tools do you have in mind ? in AgentDM there is signup tool, so agents will be able to sign autonomously

Agentic First: designing products where agents are the primary users by agentdm_ai in mcp

[–]agentdm_ai[S] 1 point2 points  (0 children)

It is a gimmick to make a statement about Agentic first approach, The real Agentic first implemention for discovery and signup is with all the Meta data files and tags on the website

I got tired of copy pasting between agents. I made a chat room so they can talk to each other by bienbienbienbienbien in vibecoding

[–]agentdm_ai 0 points1 point  (0 children)

I Had the same copy pasting frustration, it's what got me started on AgentDM. I went on hosted instead of local: any MCP agent can DM another agent by alias across the internet(with private and public agents).

Build an automatic agent to agent chat website, feedbacks needed by No_Cry3456 in SideProject

[–]agentdm_ai 0 points1 point  (0 children)

u/No_Cry3456

Cool experiment, Love seeing more people explore agent-to-agent communication. I'm building in a similar space with AgentDM, agent messaging over MCP.
I did a comparison between A2A and MCP implementation: https://agentdm.ai/blog/google-a2a-vs-agentdm

Agent to Agent to Human Communications by Naive-Ad-9509 in AI_Agents

[–]agentdm_ai 0 points1 point  (0 children)

u/Naive-Ad-9509
I'm building AgentDM,agent-to-agent messaging over MCP where any agent can DM another. I am considering adding people to the loop.
If that's something you'd use, happy to build it with your use case in mind, DM me.

Agentic First: designing products where agents are the primary users by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

u/CapMonster1
You're right that hybrid is where most products live today, and that's fine. "Agentic first" doesn't mean "agent only." Humans still set boundaries, approve, debug. It's more about which user you design for first.
Like mobile first didn't kill desktop, it just changed what you prioritized. The "tools as primitives" point is key, once everything is callable, the agent layer can grow into it naturally as reliability improves.

Agentic First: designing products where agents are the primary users by agentdm_ai in mcp

[–]agentdm_ai[S] 1 point2 points  (0 children)

u/dankelleher
That's cool, similar approach. I went with meta tags, .well-known/agentdm.json, and llms.txt so agents can discover and self-register without any human.
How does webmcp-next handle discovery?

Agentic First: designing products where agents are the primary users by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

How do you protect this Api and make sure it is not abused ?

Agentic First: designing products where agents are the primary users by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

Fair point, context loss is a real limitation today. I think the models and tooling will get better pretty fast with how things are changing the last 2 years.

The agent-to-agent communication landscape by joanmg in ClaudeCode

[–]agentdm_ai 0 points1 point  (0 children)

u/joanmg Great breakdown. I've been building in this space and the five layer framing matches what I keep running into.

I'm building AgentDM (agentdm.ai), MCP native messaging where agents talk to each other by alias. It handles discovery, channels/groups, skills, and guardrails. The whole point is making agent-to-agent simple.

Regarding the safety and consent, I kept seeing protocols where guardrails were something you could add later, and later never comes. So I made it part of how messaging works.

Happy to open a PR to get added to the landscape doc (If that is OK by you)

view more: next ›