thanks for bringing this up. I just spent 2 hours last night digging into MCP - I'd love to learn more about how you think this solves the HitL problem. From my perspective MCP is more of a protocol for tool calling over the stdio wire, and the only situation it provides HitL is when human is sitting in the desktop app observing the agent synchronously?

Again, genuinely looking to learn - where does MCP fit in for async/headless/ambient agents, beyond a solid protocol for remote tool calls?

▲

potatoman22 10 months ago | parent [-]

You could implement some blocking HitL service/tool as an MCP server.

▲

dhorthy 10 months ago | parent [-]

ah okay - I guess in that case, I would like chain a HitL step as an MCP server that wraps/chains to another tool that depends on approval?

or is there a cleaner way to do that?

▲

a1j9o94 10 months ago | parent [-]

Yeah, exactly. You would define a HitL server and the actions it implements would be API calls to your system.

	▲	dhorthy 10 months ago \| parent [-]
		this is interesting. I will have to think more about how humanlayer can support an MCP integration/wrapper, it's not immediately obvious to me i do think that AI-calling-tools is insufficient to provide bidirectional communication rails for user input/review though...not disagreeing just maybe thinking out loud a little here