Context7 Mcp

upstash/context7/packages/opencode/skills/context7-mcp

by upstashfeef1b2f6078ac8a33acd38d76817000af001373No license62K starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated today

This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.

  1. feef1b2f6078ac8a33acd38d76817000af001373Currentcommit feef1b2Published Oct 9, 2026

Source and attribution

Source:upstash/context7inpackages/opencode/skills/context7-mcpat commitfeef1b2

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from upstash/context7

Context7 Mcp

upstash

Fetches current library and framework documentation via Context7 MCP tools to answer API and code questions.

Software Development62Kupdated today

Context7 Mcp

upstash

Fetches current library and framework documentation via Context7 MCP tools instead of relying on training data.

AI & Agents62Kupdated today

Context7 Mcp

upstash

Fetches current library and framework documentation through Context7 MCP tools instead of relying on training data.

Software Development62Kupdated today

Context7 Mcp

upstash

Fetches current library and framework documentation through Context7 MCP tools instead of relying on training data.

Software Development62Kupdated today

Context7 Mcp

upstash

Fetches current library and framework documentation through Context7 MCP tools instead of relying on training data.

Software Development62Kupdated today

Find Docs

upstash

Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer — do not rely on training data for API details, signatures, or configuration options as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details.

Awaiting classification62Kupdated today