home / skills / vaayne / agent-kit / mcp-context7-docs

mcp-context7-docs skill

needs review

This skill retrieves up-to-date documentation and code examples for libraries and frameworks by querying Context7 with a resolved library ID.

npx playbooks add skill vaayne/agent-kit --skill mcp-context7-docs

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.4 KB

---
name: mcp-context7-docs
description: Query up-to-date documentation and code examples for any programming library or framework. Use when looking up API docs, finding code examples, or checking library usage. Triggers on "how to use [library]", "docs for [package]", "show me examples of [framework]", "Context7 lookup".
---

# Context7 Documentation

MCP service at `https://mcp.context7.com/mcp` (http) with 2 tools.

## Requirements

- `mh` CLI must be installed. If not available, install with:
  ```bash
  curl -fsSL https://raw.githubusercontent.com/vaayne/mcphub/main/scripts/install.sh | sh
  ```

## Usage

List tools: `mh -u https://mcp.context7.com/mcp -t http list`
Get tool details: `mh -u https://mcp.context7.com/mcp -t http inspect <tool-name>`
Invoke tool: `mh -u https://mcp.context7.com/mcp -t http invoke <tool-name> '{"param": "value"}'`

## Notes

- Run `inspect` before invoking unfamiliar tools to get full parameter schema
- Timeout: 30s default, use `--timeout <seconds>` to adjust
- **Important**: Always call `resolveLibraryId` first to get the Context7-compatible library ID before calling `queryDocs`, unless user provides ID in `/org/project` format

## Tools

| Tool               | Description                                                                                                                                                                                          |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `queryDocs`        | Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. Requires a Context7-compatible library ID obtained from `resolveLibraryId`. |
| `resolveLibraryId` | Resolves a package/product name to a Context7-compatible library ID. Must be called before `queryDocs` to get a valid library ID.                                                                    |

## Workflow

1. **Resolve library ID**: First, resolve the library name to a Context7 ID
   ```bash
   mh -u https://mcp.context7.com/mcp -t http invoke resolveLibraryId '{"libraryName": "react"}'
   ```

2. **Query documentation**: Use the resolved ID to fetch docs
   ```bash
   mh -u https://mcp.context7.com/mcp -t http invoke queryDocs '{"context7CompatibleLibraryID": "/facebook/react", "topic": "hooks"}'
   ```

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

FAQ

Do I always need resolveLibraryId before queryDocs?

Yes, unless you already provide a Context7-compatible ID in /org/project format. resolveLibraryId ensures queryDocs receives a valid ID.

What if a query returns too much content or irrelevant results?

Narrow the topic string, inspect the tool schema to refine parameters, or add filters in your query to target specific sections or versions.