​

Tools Reference

​

Overview

​

resolve-library-id

​

When to Use

• User mentions a library by name (e.g., “Next.js”, “MongoDB”, “React”)
• You need to find the Context7-compatible library ID
• User does not provide an explicit library ID in format /org/project

​

Parameters

​

Response Format

Available Libraries:

1. /vercel/next.js
   Name: Next.js
   Description: The React Framework for Production
   Code Snippets: 1,234
   Source Reputation: High
   Benchmark Score: 98
   Versions: 15.1.0, 15.0.0, 14.2.0, 14.1.0, 14.0.0

2. /nextauthjs/next-auth
   Name: NextAuth.js
   Description: Authentication for Next.js
   Code Snippets: 456
   Source Reputation: High
   Benchmark Score: 95
   Versions: 5.0.0, 4.24.0

​

Response Fields

​

Selection Process

1. Name similarity - Exact matches prioritized
2. Description relevance - Match to query intent
3. Documentation coverage - Higher Code Snippet counts preferred
4. Source reputation - High/Medium reputation more authoritative
5. Benchmark score - Higher scores indicate better quality

​

Usage Example

How do I set up authentication in Next.js?

​

Best Practices

• Provide specific, descriptive queries for better relevance ranking
• Use exact library names when possible
• Check all returned options before selecting
• If ambiguous, ask user for clarification
• Clearly state your selection and reasoning

​

Error Handling

No libraries found matching the provided name.

1. Try alternative library names or spellings
2. Check for typos in libraryName
3. Suggest related libraries to user
4. Ask user for more specific library information

​

query-docs

​

When to Use

• You have a Context7-compatible library ID from resolve-library-id
• User provides explicit library ID (e.g., /mongodb/docs, /vercel/next.js)
• You need specific documentation for a programming task

​

Prerequisites

​

Parameters

​

Response Format

## Setting Up Authentication with JWT in Express.js

### Installation

\`\`\`bash
npm install jsonwebtoken express
\`\`\`

### Basic JWT Middleware

\`\`\`javascript
const jwt = require('jsonwebtoken');
const express = require('express');

const authenticateToken = (req, res, next) => {
  const authHeader = req.headers['authorization'];
  const token = authHeader && authHeader.split(' ')[1];

  if (!token) return res.sendStatus(401);

  jwt.verify(token, process.env.ACCESS_TOKEN_SECRET, (err, user) => {
    if (err) return res.sendStatus(403);
    req.user = user;
    next();
  });
};

app.use(authenticateToken);
\`\`\`

### Generating Tokens

\`\`\`javascript
const token = jwt.sign(
  { userId: user.id }, 
  process.env.ACCESS_TOKEN_SECRET,
  { expiresIn: '1h' }
);
\`\`\`

[Documentation Source: Express.js Authentication Guide]

• Relevant code examples
• API references
• Configuration instructions
• Best practices
• Links to source documentation

​

Usage Example

Create a Next.js middleware that checks for a valid JWT in cookies.

​

Version-Specific Queries

{
  "libraryId": "/vercel/next.js",
  "query": "How to use App Router?"
}

How do I set up Next.js 14 middleware? use context7

​

Best Practices

• Be specific in your queries for better results
• Include context about what you’re trying to accomplish
• Mention versions when relevant
• Ask focused questions rather than broad topics
• Use technical terms that appear in documentation

​

Error Handling

Documentation not found or not finalized for this library. 
This might have happened because you used an invalid Context7-compatible library ID.
To get a valid Context7-compatible library ID, use the 'resolve-library-id' 
with the package name you wish to retrieve documentation for.

1. Verify library ID format is /org/project
2. Call resolve-library-id to get the correct ID
3. Check if the library exists in Context7

The library you are trying to access does not exist. 
Please try with a different library ID.

1. Try searching with resolve-library-id
2. Verify library name spelling
3. Check if library is available in Context7 catalog

​

Tool Workflow

​

Complete Example

Create a MongoDB connection with connection pooling in Node.js

{
  "name": "resolve-library-id",
  "arguments": {
    "query": "Create a MongoDB connection with connection pooling",
    "libraryName": "mongodb"
  }
}

{
  "name": "query-docs",
  "arguments": {
    "libraryId": "/mongodb/docs",
    "query": "MongoDB connection pooling configuration in Node.js"
  }
}

​

With Explicit Library ID

Implement basic authentication with Supabase. 
use library /supabase/supabase for API and docs.

{
  "name": "query-docs",
  "arguments": {
    "libraryId": "/supabase/supabase",
    "query": "Implement basic authentication with Supabase"
  }
}

​

Rate Limiting

• Anonymous: Limited requests per hour
• Free API Key: Higher limits suitable for development
• Paid Plans: Professional and enterprise limits

​

Privacy & Security

• Intelligent reranking of documentation
• Context generation
• Relevance scoring

​

Annotations

• Do not modify any data
• Only retrieve information
• Are safe to call multiple times
• Have no side effects

​

Next Steps