Agent Skills (the SKILL.md format) are reusable instruction packages: They teach an agent to complete a task with a defined approach.
MCP is the live protocol through which an agent reaches the tools and data of someone else's software. Skills govern the approach, MCP provides the access.
For SaaS vendors the order is unambiguous: Without an MCP endpoint there is nothing for a skill to be applied to.
The combination is the end state: An official skill that teaches the use of your endpoint is product documentation for agents.
Since Anthropic introduced the Agent Skills format (SKILL.md plus scripts and resources), German SaaS teams have been asking a fair question: Do we need this now instead of MCP? The short answer: No. The long answer is worth it, because the two things sit on different layers and the confusion can get expensive.
Skills: the approach as a package
An agent skill is an instruction package that teaches an agent how a specific task is done correctly in professional terms: which steps, which quality criteria, which special cases. Skills are reusable, versionable, and shared. The market already treats them as a standard of their own, with their own directories.
Skills solve a knowledge problem. Afterwards, the agent knows, for example, how a factual payment reminder is phrased or which review sequence applies before a cancellation.
MCP: access as a protocol
MCP solves an access problem. Without MCP, a language model can read and write text; with MCP it gets tools: search invoice, create draft, change address, authenticated on behalf of a user, with that user's permissions, with an audit log. The chain from the 401 to the login is specified, and tool descriptions are the part through which the agent decides which tool it chooses when.
Why the layers are not interchangeable
A skill without MCP is procedural knowledge without hands: The agent knows how a payment reminder is structured but cannot create one in your system. An MCP endpoint without a skill is access without an approach: The agent can search invoices but does so without your firm's domain knowledge.
For you as a software vendor, a clear order follows:
- First the endpoint. It is the interface your customers need for every agent integration, regardless of which skill ecosystem wins.
- Then the descriptions. Tool descriptions are your real skills: They must be correct out of the software itself, regression-tested with model clients.
- Optionally an official skill. A SKILL.md package that teaches the use of your endpoint is product documentation for agents. It presupposes what you built first.
The Deutscher MCP-Report 2026 shows where the field stands: 4 of 21 audited providers have an MCP endpoint of their own, and the median of the field is 8 out of 100 points. Nobody in this field is discussing skills right now, because the access layer is missing.
→ The first building block is the access layer: The free live test shows in under a minute whether your API already has it.