mcp-context7-docs_skill

Overview

This skill lets you query up-to-date documentation and code examples for any programming library or framework using the Context7 MCP service. It resolves package names to Context7-compatible IDs and fetches targeted docs or example snippets. Use it when you need authoritative API references, sample code, or usage patterns quickly.

How this skill works

First, call resolveLibraryId to convert a package or product name into a Context7-compatible library ID. Then call queryDocs with that ID and a topic or query string to retrieve relevant documentation and code examples. The service returns structured docs; inspect the tool schema before invoking unfamiliar parameters and adjust timeouts as needed.

When to use it

• Looking up API docs for a specific library or framework
• Finding real code examples and usage patterns for components or functions
• Checking the latest official documentation for breaking changes or new features
• Preparing code snippets for tutorials, PRs, or design discussions
• Validating library usage when migrating or upgrading dependencies

Best practices

• Always call resolveLibraryId first to obtain the required Context7-compatible ID unless you already have /org/project format
• Run inspect on a tool before invoking to understand required parameters and response shape
• Use concise, specific topics (e.g., "hooks" or "routing") to get focused results
• Set a longer timeout for large queries or slow network using --timeout <seconds>
• Treat returned examples as a starting point and verify against your target library version

Example use cases

• Resolve "react" to /facebook/react, then queryDocs for "hooks" to get examples for useState and useEffect
• Look up docs for a lesser-known package name by resolving its library ID first, then fetch API reference
• Fetch component usage examples for a UI framework when writing documentation or examples
• Verify method signatures and parameter names when updating callers across a codebase
• Search for migration guidance or deprecation notes when upgrading a dependency