# Agent protocols beyond MCP in Julia?

**URL:** <https://discourse.julialang.org/t/agent-protocols-beyond-mcp-in-julia/139563>\
**Category:** Tooling\
**Tags:** question, ai, agent\
**Created:** [September 19, 2026, 6:24am UTC](https://discourse.julialang.org/t/agent-protocols-beyond-mcp-in-julia/139563 "2026-09-19T06:24:35Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![scelles](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/scelles/32/220408_2.png) [@scelles](https://discourse.julialang.org/u/scelles)\
**Post date:** [September 19, 2026, 6:24am UTC](https://discourse.julialang.org/t/agent-protocols-beyond-mcp-in-julia/139563/1 "2026-09-19T06:24:35Z")

</div>

Hello,

I’ve been looking at some of the emerging agent protocols beyond [MCP](https://modelcontextprotocol.io/): **[AG-UI](https://www.copilotkit.ai/ag-ui), [A2UI](https://a2ui.org/), [Agent Client Protocol](https://agentclientprotocol.com/) (ACP), [Agent Control Protocol](https://acp-protocol.org/) (also ACP), and [Agent2Agent](https://a2a-protocol.org/) (A2A)**.

I haven’t seen much discussion about them in the Julia ecosystem yet. Is anyone already experimenting with or implementing any of these?

I’m asking partly in the context of [ManyUI.jl](https://juliatryit.github.io/ManyUIDoc.jl/dev/), as some of these protocols seem like they could fit naturally with the idea of defining an application/UI once and exposing it through CLI, TUI, Web, or potentially to AI agents.

---

<div class="post-metadata">

**Author:** ![dcelisgarza](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dcelisgarza/32/215951_2.png) [@dcelisgarza](https://discourse.julialang.org/u/dcelisgarza)\
**Post date:** [September 19, 2026, 6:59am UTC](https://discourse.julialang.org/t/agent-protocols-beyond-mcp-in-julia/139563/2 "2026-09-19T06:59:01Z")

</div>

Kaimon.jl and KaimonSlate.jl are the de-facto MCP and Agent-enabled notebook respectively.

---

<div class="post-metadata">

**Author:** ![madppiper](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/madppiper/32/220029_2.png) [@madppiper](https://discourse.julialang.org/u/madppiper)\
**Post date:** [September 19, 2026, 9:10am UTC](https://discourse.julialang.org/t/agent-protocols-beyond-mcp-in-julia/139563/3 "2026-09-19T09:10:18Z")

</div>

There is also an MCP integration into the [Flexible Julia](https://plugins.jetbrains.com/plugin/29356-flexible-julia/) plugin for JetBrains IDEs if you care to look at those.

---

<div class="post-metadata">

**Author:** ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)\
**Post date:** [September 19, 2026, 3:34pm UTC](https://discourse.julialang.org/t/agent-protocols-beyond-mcp-in-julia/139563/4 "2026-09-19T15:34:22Z")

</div>

I’m preparing the release of BonitoAgents, which comes with its own Julia mcp and also an agent client protocol implementation. It’s also a hybrid between notebook and normal agent chat:  
[agents.bonito.sh](https://agents.bonito.sh)

---

<div class="post-metadata">

**Author:** ![kahliburke](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kahliburke/32/208472_2.png) [@kahliburke](https://discourse.julialang.org/u/kahliburke)\
**Post date:** [September 19, 2026, 7:02pm UTC](https://discourse.julialang.org/t/agent-protocols-beyond-mcp-in-julia/139563/5 "2026-09-19T19:02:41Z")

</div>

> [@scelles](#):
>
> I’ve been looking at some of the emerging agent protocols beyond [MCP](https://modelcontextprotocol.io/): **[AG-UI](https://www.copilotkit.ai/ag-ui), [A2UI](https://a2ui.org/), [Agent Client Protocol](https://agentclientprotocol.com/) (ACP),**

ACP is coming very soon to the Kaimon multiverse! This will allow fine grained control of agents, expanded agent support for open code and other ACP compliant packages, specialist agent roles and tool control, and more.

If any of these other protocols are particularly useful or capable, and generally fit into the “vibe” of my packages, I would definitely consider supporting them. I’m responsive to community feedback and requests, if there’s something you’d like to see, let me know!

---

<div class="post-metadata">

**Author:** ![technocrat](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/technocrat/32/220947_2.png) [@technocrat](https://discourse.julialang.org/u/technocrat)\
**Post date:** [September 19, 2026, 11:43pm UTC](https://discourse.julialang.org/t/agent-protocols-beyond-mcp-in-julia/139563/6 "2026-09-19T23:43:52Z")

</div>

Wicked. I prompted asking “Design a Conway’s Game of Life that uses fractals.” What I got wasn’t quite what I had in mind (which is pretty fuzzy, because what does it even mean for two fractals to collide) but turned out to be a 3N dimensional version, where a layer’s substrate influences life, birth, death, infinity. (You are not expected to catch that cultural reference unless you are close to Boomer grandparents.) What impressed was 129 `@test` statements across 15 testsets.

---

<div class="post-metadata">

**Author:** ![gregvectle](https://avatars.discourse-cdn.com/v4/letter/g/8e7dd6/32.png) [@gregvectle](https://discourse.julialang.org/u/gregvectle)\
**Post date:** [September 22, 2026, 2:04pm UTC](https://discourse.julialang.org/t/agent-protocols-beyond-mcp-in-julia/139563/7 "2026-09-22T14:04:51Z")

</div>

one distinction that helped me keep these straight: they live at different layers. MCP is tools and data, ACP is editor to agent, A2A is agent to agent, and AG-UI is agent to frontend, basically streaming events into a UI. so for the ManyUI.jl idea you mentioned, AG-UI is probably the most natural fit since thats exactly what its designed for. A2A is just JSON-RPC under the hood so interop from julia is straightforward even without a dedicated client package.

---

<div class="post-metadata">

**Author:** ![floswald](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/floswald/32/195_2.png) [@floswald](https://discourse.julialang.org/u/floswald)\
**Post date:** [September 26, 2026, 2:16pm UTC](https://discourse.julialang.org/t/agent-protocols-beyond-mcp-in-julia/139563/8 "2026-09-26T14:16:53Z")

</div>

looks amazing! thanks for that

---

<div class="post-metadata">

**Author:** ![kahliburke](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kahliburke/32/208472_2.png) [@kahliburke](https://discourse.julialang.org/u/kahliburke)\
**Post date:** [September 27, 2026, 2:44am UTC](https://discourse.julialang.org/t/agent-protocols-beyond-mcp-in-julia/139563/9 "2026-09-27T02:44:39Z")

</div>

Note that Kaimon v1.9.0 released a few days ago now supports ACP, described here:

> **[ACP agents ​ - AI Agent Sessions | Kaimon.jl](https://kahliburke.github.io/Kaimon.jl/dev/agents#ACP-agents)**
>
> Kaimon can spawn and own AI agent sessions – a headless coding agent that you talk to programmatically. Kaimon launches the agent, normalizes its output into a vendor-neutral event model, streams those events on the gate event bus, and tracks each...

Any Julia session attached via the Gate can use this feature to have programmatic control over starting, managing, guiding, and stopping agents. This is being integrated into several new KaimonSlate features which will be released in the near future. The `hpc_cluster` branch already has some examples of this for anyone wanting to experiment now.

Since this ACP capability is new functionality that I’m starting to leverage, there will likely be additional features and enhancements to it in the coming weeks. Feedback and bug reports are welcome, of course.