apify / mcpc

The mcpc skill documents the CLI end to end: connecting to a remote or local MCP server as a named session, listing and calling its tools, reading resources, running prompts and async tasks, and a --json mode meant for scripting rather than a human terminal. It assumes the @apify/mcpc npm package is already installed (Node.js 22+ or Bun) — the skill teaches the commands, not the install step. The second skill, record-demo, is not a usage guide at all: it drives VHS to record or refresh the terminal GIFs that appear in the repository's own README, authenticating with a short-lived test token rather than a production one.

This is for an agent, or someone driving one, that already needs to talk to MCP servers over a shell and wants one consistent CLI across all of them instead of separate MCP client wiring per server. record-demo has no purpose outside apify's own repository maintenance, and neither skill does anything without a JavaScript runtime already on the machine.

READ THE FULL ANALYSIS＋

Effectively one of the two shipped skills is general-purpose. record-demo exists to keep apify's own documentation current, not to help an agent use mcpc — it is the maintainers' own tooling, packaged as a skill alongside the real one.