Context7 MCP: Live Library Docs for Claude Code

What is upstash/context7, actually

upstash/context7 is the repository behind Context7, described in its own summary as a platform for up to date code documentation for LLMs and AI code editors (61,207 GitHub stars). Flowy files it under the documentation category, which is exactly what it is: a way to hand an agent a library's current API instead of whatever a model learned during training. Training data has a cutoff date, and real documentation keeps moving after that date, so a model can describe a method that was renamed two releases ago or invent one that never existed. Context7 exists to close that gap by fetching documentation and code examples at the moment they are needed.

The plugin Flowy indexes is 8 components: one MCP server, four skills, two agents, and one command, all different ways of asking the same two questions: which library is this, and what does its documentation say right now.

The MCP server underneath everything

context7 is the MCP server the rest of the plugin sits on top of. The fact pack Flowy indexed carries no one line description for this entry specifically, so this part comes from the repository itself rather than an indexed description: the server matches a library name to the documentation source Context7 tracks for it, then returns the passage or code example relevant to the question asked. Every skill, both agents, and the command below are ways of triggering that same lookup. None of them replace it.

The four skills, and why three barely differ

Three of the four skills, context7-docs, find-docs, and context7-mcp, describe close to the same job in different words: fetch up to date documentation, API references, and code examples the moment a user asks about a specific library, framework, SDK, CLI tool, or cloud service. Their own descriptions even list the same kind of examples, React, Next.js, Prisma, Express, Tailwind, Django, Spring Boot, Vue, and Supabase, as libraries worth checking even though a model already recognizes the name. The fact pack does not explain why the plugin ships three separate skills for one job, so treat this as one capability with three trigger phrases rather than three distinct tools.

context7-cli is the one that actually differs. Its own description covers a command line tool, named ctx7 in the description text, used to fetch library documentation, manage AI coding skills, and configure the Context7 MCP connection itself. It triggers on someone naming "ctx7" or "context7" directly, not only on a library question, which makes it the entry point for setup and configuration rather than a single lookup.

The two agents and the one command

docs-researcher and docs-researcher.agent carry the identical one line description in what Flowy indexed: a lightweight agent for fetching library documentation without cluttering the main conversation. The fact pack does not explain why the plugin registers what reads like the same agent under two names, so treat it as one dispatch target reachable two ways, useful for sending a long documentation fetch off to its own side conversation instead of filling up the thread someone is reading.

The docs command is the direct version of the same idea. Its own description is short: look up documentation for any library. It is a one line entry point into the same MCP server for someone who wants to type a request instead of waiting for a skill to notice a library name in conversation.

When would I actually reach for this

If a library question comes up naturally, the skills fire without any action from you, and which of the three near identical ones fires depends on how its trigger phrase was written, not on anything you choose. If you already know you want documentation and nothing else, the docs command or the docs-researcher agent skip straight to it, and the agent is the better pick when the fetch is likely to run long. Reach for context7-cli specifically when the job is setting up or configuring Context7 itself, or when you are working from a terminal rather than a chat.

How do I install it

Flowy indexes upstash/context7 from its public GitHub repository. It does not own, bundle, or host Context7, and the documentation lookups happen through Context7's own service once the MCP connection is live, not inside Flowy. Install from the listing page linked at the top of this guide, and all 8 components above, the MCP server, all four skills, both agents, and the command, become available in that session.