using-docs-mcp

Instructions for using search and document-retrieval tools that index current React or React Native documentation. React and React Native are JavaScript tools for building web and mobile interfaces.

In plain words
What is it for?
Searching for API guidance, narrowing results to documentation sections, opening relevant pages, and retrieving fuller instructions for migrations or multi-step procedures.
Why use it?
It reduces reliance on possibly outdated remembered API details by checking the live indexed documentation before writing code.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/sannnao/react-docs-mcp/using-docs-mcp
Any agent
npx skills add Sannnao/react-docs-mcp --skill using-docs-mcp
Clone the repo
git clone --depth 1 https://github.com/Sannnao/react-docs-mcp

Made for: Claude Code, Codex.

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 509 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.00509
Opus 5 $0.00022 $0.00254
Sonnet 5 $0.00009 $0.00102
Haiku 4.5 $0.00004 $0.00051

Measured 3d ago against content hash 7896ebb1f79e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

using-docs-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/using-docs-mcp/SKILL.md · 18 lines

How it starts

The opening of the file, as written. The whole thing — 18 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Using react-docs-mcp / react-native-docs-mcp

When these MCP servers are connected, prefer them over recalling React or React Native APIs from memory — training data goes stale, these tools index the live docs repo.

Workflow

  1. Search first. Call search_react_docs (or search_react_native_docs) with a natural-language query before writing any React/React Native code that touches an API you're not 100% certain about. Results include a relevance-ranked snippet and a url.
  2. Drill in only when needed. If the search snippet isn't enough, call get_doc with the path from a search result. It returns a ~1500 char summary plus a structure outline by default — enough for most questions.
  3. Use full: true sparingly. Pass full: true to get_doc only when the summary likely cuts off something you need — long migration/upgrade guides, multi-step setup pages, or anything with many sequential steps where truncation would hide later steps. Don't default to full for every call; it costs more context for no benefit on short reference pages.
  4. Filter by section when you know the area. section narrows results (e.g. learn/reference/blog/community for React; the-new-architecture/legacy/releases for React Native). For React Native, most pages have no section — search unfiltered unless you're specifically after one of those three areas.
  5. Pin React Native docs to the user's actual version when it matters. If the project's installed react-native version is known and differs from latest, and the question is about an API that may have changed across versions, note that react-native-docs-mcp can be started with --docs-version=X.YY to index that release's frozen docs snapshot instead of always-current — mention this to the user rather than silently assuming latest-version behavior applies to their older app.
  6. Refresh if docs seem stale or contradict recent framework changes. Call update_docs to pull the latest commit before concluding an API doesn't exist.

Read the full file on GitHub · 18 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 18 lines · 44 tokens per session scan A 7896ebb1f79e

Subscribe to this mod's changes

using-docs-mcp is a skill published in the GitHub repository Sannnao/react-docs-mcp (8 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 509 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

using-react-hook-form-docs-mcp

How to effectively use the react-hook-form-docs-mcp search and doc-retrieval tools instead of relying on training-data memory of React Hook Form APIs.

Sannnao/react-hook-form-docs-mcp · 41 tokens

using-react-native-docs-mcp

How to effectively use the react-native-docs-mcp search and doc-retrieval tools instead of relying on training-data memory of React Native APIs.

Sannnao/react-native-docs-mcp · 38 tokens

tamagui

Universal React UI framework for web and native. Use when building cross-platform apps with Tamagui, creating styled components with styled(), configuring design tokens/themes, using Tamagui UI components, or working with animations. Triggers: "tamagui", "styled()", "$token", "XStack/YStack", "useTheme", "@tamagui/"…

tamagui/tamagui · 90 tokens

truesheet-usage

Consumer-side guide for integrating @lodev09/react-native-true-sheet into a React Native app. Use this skill whenever the user wants to add, configure, control, or debug a bottom sheet using TrueSheet — including ref-based sheets, named global sheets, web support with TrueSheetProvider/useTrueSheet, React Navigation…

lodev09/react-native-true-sheet · 169 tokens

writing-react-native-storybook-stories

Create and edit React Native Storybook stories using Component Story Format (CSF). Use when writing .stories.tsx files, adding stories to React Native components, configuring Storybook addons (controls, actions, backgrounds, notes), setting up argTypes, decorators, parameters, or working with portable stories for…

storybookjs/react-native · 83 tokens

setup-react-native-storybook

Set up Storybook for React Native in Expo, React Native CLI, or Re.Pack projects. Use when adding Storybook to a project, configuring metro.config.js with withStorybook, creating .rnstorybook configuration files, setting up Storybook routes in Expo Router, configuring getStorybookUI, or adding the StorybookPlugin to a…

storybookjs/react-native · 102 tokens