-
-
Notifications
You must be signed in to change notification settings - Fork 70
Open
Description
Question
The dev-2.0 branch has a full MCP server implementation (HTTP + SSE). However, many modern AI tools now support skill-based architectures that provide similar functionality without server overhead.
Concerns
- MCP requires maintaining HTTP server lifecycle
- Skills can achieve similar tool-calling with less complexity
- Long-term maintenance burden
Discussion Points
- Are there MCP-specific features that skills cannot replace?
- How many users actively rely on MCP integration?
- Would a hybrid or migration path make sense?
Not suggesting immediate removal - just want to discuss the long-term architecture direction.
Contact: ocarina1024@gmail.com
Metadata
Metadata
Assignees
Labels
No labels