React Analyzer MCP vs Context7
A side-by-side look at the React Analyzer MCP and Context7 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose React Analyzer MCP for developer tools work; choose Context7 for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose React Analyzer MCP when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
- You want tools like
analyze-react, analyze-project, list-projects.
Choose Context7 when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
resolve-library-id, query-docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 47/100 · Fair | 65/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 58 | 63,150 |
| Directory activity | 8 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View React Analyzer MCP | View Context7 |
Tools & capabilities
React Analyzer MCP tools 3
analyze-reactAnalyzes a single React component from source codeanalyze-projectGenerates documentation for all React components in a project folderlist-projectsLists all projects under the root folder
Context7 tools 2
resolve-library-idResolves a general library name into a Context7-compatible library ID.query-docsRetrieves documentation for a library using a Context7-compatible library ID.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
React Analyzer MCP
No confirmed install command for React Analyzer MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Context7
{
"mcpServers": {
"upstash-context7": {
"command": "npx",
"args": [
"-y",
"ctx7"
]
}
}
}
Frequently asked questions
React Analyzer MCP is categorized under Developer Tools and uses an install path we have not confirmed yet. Context7 belongs to Developer Tools and uses a local stdio subprocess. Pick React Analyzer MCP for developer tools work and Context7 for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. React Analyzer MCP has no confirmed install command yet — follow its own setup instructions.
React Analyzer MCP is listed as free. Auth: no auth required. Context7 is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add azer-react-analyzer-mcp and upstash-context7 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, React Analyzer MCP has a quality signal of 47/100 (Fair) with 8 views, 0 installs and 58 GitHub stars. Context7 has 65/100 (Great) with 9 views, 0 installs and 63,150 GitHub stars.