| FMRS | 55 / 100 · C | 80 / 100 · B | 79 / 100 · B |
|---|
| Reliability | 9 / 20 | 14 / 20 | 12 / 20 |
|---|
| Security and permissions | 11 / 20 | 16 / 20 | 16 / 20 |
|---|
| Maintenance | 10 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 12 / 20 | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 18 / 20 | 15 / 20 |
|---|
| Best for | - MCP client users who want an independent Grok 4.7 opinion
- Users who need exact control over model ID, reasoning effort, and output-token ceiling and accept metered billing
- Developers who already hold an xAI API key or have the official Grok CLI installed
| - Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
- Scenarios wanting zero-config documentation lookup
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Users unwilling to pay metered API costs and looking only for free usage
- Users needing automatic failover or multi-provider fallback — this server offers no harness or model fallback
- Users who can neither provide XAI_API_KEY nor install grok-cli
- Users who need fully offline or private local inference (a local provider would be a better fit)
| - Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
- Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - Requires the XAI_API_KEY secret environment variable, used only for requests to https://api.x.ai
- If the grok-cli harness is used, requires an installed and authenticated official Grok CLI
- Launched as a stdio process by the local MCP client from the npm package @ask-llm/grok-mcp
| - Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
- Read-only documentation lookup — no code execution or local filesystem access involved
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - The xAI API is metered and paid; prompt and response length directly affect cost, and ASK_GROK_MAX_OUTPUT_TOKENS only bounds accidental spend
- XAI_API_KEY is a secret; if leaked, others could consume your quota
- The server never falls back to another harness or model, so a misconfiguration causes failure rather than degradation
- Grok's answers come from a third-party tool that is not an official xAI product; verify output accuracy yourself
- Prompt content is sent to xAI's service, so treat sensitive code or data with care
| - The free tier has limited quota — high-frequency use may hit rate limits
- Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | Claude Code, Claude Desktop, Cursor, Codex, Pi | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 1 | 2 | 19 |
|---|