|
|
|
|
|
by Xelynega
443 days ago
|
|
> And because this can now happen at runtime, users (instead of developers) can add arbitrary functionality to applications. I don't understand what you mean by this. Currently without MCP a server has an API that's documented and to interact with it(thus provide "arbitrary functionality") you call those APIs from your own application code(e.x. python script). With MCP an LLM connected to your application code calls an API that's documented via MCP to provide "arbitrary functionality". How are these different, and how does MCP allow me to do anything I couldn't before with API access and documentation? In both cases the application code needs to be modified to account for the new functionality, unless you're also using the LLM to handle the logic which will have very unpredictable results. |
|
In the case of MCP, no application code is modified. You first ship the application and then functionality is added. Using plain APIs, it's the other way around. That's the difference.