M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionAsk Grok MCP ServerConsult Grok through xAI's metered API with exact model selection and no fallbackGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS55 / 100 · C76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions11 / 2014 / 20
Maintenance10 / 2018 / 20
Documentation12 / 2017 / 20
Setup experience13 / 2014 / 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
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
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)
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
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
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
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
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Code, Claude Desktop, Cursor, Codex, PiClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools115