I Built a CLI That Gives Your LLM Accurate Library Docs — No MCP Server Needed

The Problem You're building with Next.js 15 and ask your AI assistant to write an API route. It gives you the Pages Router pattern from Next.js 12. You paste React docs into the prompt, but they're already outdated by the time you copy them. Context7 solved this by indexing documentation directly from source repos and serving it through an MCP server. Cursor, Claude Code, and other AI editors use it to get real, version-specific docs instead of hallucinated APIs. But MCP has a constraint: you need an MCP-compatible client. If you're working in the terminal, running a script, or using a local LLM — you're out of luck. The Solution I built c7 — a CLI that pulls from the same Context7 database and outputs docs as plain text to stdout. c7 react hooks c7 express middleware c7 nextjs "app router" That's it. No server, no configuration, no IDE integration. Just text you can pipe anywhere. How It Works The CLI does two things: Resolves a library name to a Context7 ID (e.g., react → /websites/r