Everyone calls it chat. I am technical and even I’ve come around to calling it that because that is what everyone, including very technical people, call the product.
Just this this weekend got a cabin on the Mississippi and went totally no phones or tv. Wife and I spent the weekend reading, doing yoga and playing checkers.
Mcp just wraps the existing calls with a description of when to use them. Why would you write a cli for something like this? And clis generally have a help call but that doesn’t say when to use a tool just what it does
You first authenticate via the phone (you can run an initial api call on phone start,) save session credentials in state on 11labs side and can then pass them back to future tool calls. You can then authenticate via a passcode if you wish
I often find that a lot of models will call the `--help` flag to figure out the commands and arguments nowadays. If I use a cli repeatedly, I'll generally ask it to create a skill
My company uses MCP in production to connect different AI products together that were developed by different teams. It makes the connections very easy, where a REST interface often has quirks and features that you have to understand.
That's fair. REST isn't much of a standard. MCP can be just as badly designed and documented as REST, but at least there's a standard for authenticating and listing the options. Reading through other top-level comments, this seems to be the theme. MCP usage is mostly driven by ease of connection.
Basically it's just bundling the API documentation into a standard format to plug into LLMs, if you're comfortable running prompt injection on yourself and downloading random text from random websites and telling your favorite LLM to use it to access your banking information.
fwiw I thought it was a good analogy. Sure splitting a company is possible and scrambling an omelette is not, but it sure takes a lot more effort to effectively undo entropy.
In a merger you can take as long as you want to go from
1. Two separate companies except at the end of the quarter we add their revenue and expenses together in a spreadsheet to transition to
2. One fully integrated organization
And usually you are becoming more efficient and saving time and money as you integrate.
Splitting a company needs to happen quickly or you'd get all sorts of weird effects where coworkers are ostensibly competitors whilst sharing resources during the transition. And you have to expend a huge amount of effort. Just a couple random complex systems that need to be untangled off the top of my head: physical property and leases, IP space for every IT service you run, multi-year contracts with every vendor from janitorial to SaaS, multi year contracts with customers depending on how the split goes, and of course all the intermingled finances and HR and spreadsheets every company in the world lives on. I'm sure there's thousands more considerations.
I agree antitrust is a big problem that needs to be solved. But "it should be the same amount of effort to merge and split a company" is just fantasy.
reply