mcp-research

Retrieve current library and API documentation via MCP tools.

5|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/ahgraber/skills --skill mcp-research-ahgraber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-research
Source: https://github.com/ahgraber/skills/tree/main/skills/mcp-research
Command: npx skills add https://github.com/ahgraber/skills --skill mcp-research-ahgraber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MCP-based tools provide current, source-backed information for libraries, APIs, and ecosystems, replacing outdated knowledge with verifiable guidance.

Core Features & Use Cases

  • Retrieve official documentation, version notes, and migration guidance for libraries and frameworks.
  • Verify code examples and API usage against primary sources across Context7, Exa, and Jina workflows.
  • Provide verified, actionable guidance with citations and links to sources.

Quick Start

Ask MCP to fetch the latest, official documentation for a library or API.

Frequently Asked Questions about mcp-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch current library documentation for a specific framework version?

Fetch current library documentation by asking the MCP research tools to retrieve official docs, version notes, and migration guidance for the specified framework, ensuring the information is source-backed and verifiable.

How do I verify API usage and code examples against official sources?

Verify API usage and code examples by corroborating tool results across Context7, Exa, and Jina workflows against primary sources to provide verified, actionable guidance with citations and links.

Can I get version migration guidance for outdated library dependencies?

Get version migration guidance for outdated library dependencies by retrieving official documentation and version notes through MCP tools, which replace stale knowledge with current, source-backed information to prevent misleading migrations.

What's the best way to ensure framework usage guidance is not outdated?

Ensure framework usage guidance is not outdated by consulting official docs through MCP-based tools, which replace outdated knowledge with verifiable guidance corroborated by primary sources.

Do I need specific MCP tools to check dependency versions and API docs?

Checking dependency versions and API docs requires MCP-based tools that fetch current, source-backed information across Context7, Exa, and Jina workflows to ensure answers are verifiable.

Why does stale knowledge mislead library version migrations?

Stale knowledge misleads library version migrations because it lacks current, source-backed information, making it necessary to consult official docs and corroborate tool results to ensure verified, actionable guidance.