Adam Stacoviak

You said it was calling for this feature set that wasn't there, and that's why you had to go that route.

Well, don't go into the details necessarily about that, but what does it do?

What does it enable for the MCP?

Why is it in the protocol?

Is it the point of dynamic client registration to enable the MCP server to spin up whenever you launch it or initiate it or instantiate it to attach itself to the tail net?

Is that the point of this dynamic client registration?

Or is it the individuals coming into the MCP, maybe through a CLI or other agentic workflows?

been more about us just allowing you know what i don't have a great answer for you on that one that's okay that's okay i'm worried i'm gonna i'm trying to pick it up with you because this is you know when you're in the land of burgeoning right you you kind of have to navigate some seaweed and uh some tall grass and you got to get your hatchet on you're like you know what i don't really know where i'm at right now this is moving so fast what is the point of this

That's what I'm curious about because it seems like that might be the case.

I see a lot of folks delivering a CLI and a MCP in one.

A lot of Go applications are doing this or Go CLIs are doing this where they'll deliver a CLI and MCP server in one single thing and you can launch it via the CLI, which is pretty easy.

And I'd imagine you want that thing to authenticate.

with a tail net.

If I'm setting up a network, I want it to have an identity.

Be the MCP server for XYZ server or service, and that's who you are, and you've got ACLs and identity attached to you.

Take me back into TS IDP.

You mentioned not wanting to be an IDP.

These are acronyms, everybody, okay?

I think it's, what does IDP stand for?

Identity... Provider.