Both MCP and Skills extend what an agent can do. But they solve different problems, and picking the wrong one adds cost or complexity you don't need.
The diagram breaks down the five dimensions that matter.
1. Integration: MCP is a client-server protocol that connects N agents to M backends through one interface. Agent Skills are folders with a SKILL. md that the agent loads on trigger.
2. Architecture: MCP runs as a separate process with its own runtime, speaking JSON-RPC. A Skill is just a directory: SKILL. md, optional scripts, references, and assets.
3. Invocation: MCP tools are called with typed parameters validated against a schema, and can be chained. Skills are invoked by the agent reading SKILL. md and running whatever commands it describes like bash, python, or curl.
4. Runtime: MCP servers often run in their own container or service. Skills run in the agent's own environment with no extra infra.
5. Where it fits: Use MCP to connect agents to live systems and data. Use Skills to give agents reusable know-how and instructions.
No comments:
Post a Comment