MCP vs. Skills
A good breakdown of the MCP vs. Skills tradeoffs from David Mohl:
Skills are great for pure knowledge and teaching an LLM how to use an existing tool. But for giving an LLM actual access to services, the Model Context Protocol (MCP) is the far superior, more pragmatic architectural choice.
In practice, some publishers aren’t forcing the choice. Wiley’s Knowledge Nexus offers both — MCP if you want to point an LLM at it directly, API if you’d rather build your own integration. Whichever fits your stack is probably fine.