Use mcp2cli when an agent needs to inspect or call an existing MCP server, OpenAPI spec, or GraphQL endpoint from the shell right away. It discovers commands at runtime, handles auth patterns including headers and OAuth, and gives the agent a small CLI surface it can script, retry, and pipe through other terminal tools.

This is skill-shaped because the job is narrow and repeatable: adapt an already-existing endpoint into a temporary command-line interface for shell-first automation. It is not a generic API framework listing, SDK generator card, server-hosting product, or long-lived integration platform entry. Invoke it when the blocker is missing CLI ergonomics around an existing endpoint, not when you need to design the API, publish a server, or build a permanent client library.