Should AI agent tools be packages instead of MCP services?
After building separate tools for several AI s, the next step was to combine them in a local MCP server. The setup became cumbersome because the MCP service appeared to need its own controls, including different for different levels of control, while the client also required . This led to the view that model tools should be loaded directly by an instead of separate services.
The comparison is a program checking the current time through its language’s built-in library rather than calling a dedicated web service. Each would need its own package, but that tradeoff already exists for many ordinary software tools.
Key points
- Separate AI tools were being replaced with one local MCP server.
- levels and can add on both the service and s.
- The proposed alternative is to load model tools as inside each .
- Separate packages would be needed for different s.
- No token-use or cost comparison was provided.