← Back to directory
A

Ask LLM Claude MCP Server

Community
Read-only Claude second opinions for non-Claude MCP clients via Claude Code CLI
Category
Dev Tools #95 of 438
Stars
★ 18 Very popular
Transport
stdio (local process)
Runtime
Node.js 20+
Credentials
API key / credential required
License
MIT
Last commit
Tools
3
62FMRS · C

Ask LLM Claude MCP Server is one of the seven MCP servers in the same repository, with a narrow, clear scope: it gives non-Claude MCP clients a read-only consulting channel to the Claude Code CLI. It exposes only ask-claude, ping, and get-usage-stats, and its manifest declares four optional environment variables covering model, fallback, timeout, and log level. It is simple and restrained in permissions (Read/Glob/Grep), which suits using Claude as an independent reviewer. The limits are equally clear: it requires a separately installed and authenticated Claude Code CLI, consumes that quota, sends data to Claude, and is unofficial at version 0.0.1.

Strongest · Documentation 14/20 Weakest · Reliability 9/20

Reliability
9/20
Security and permissions
13/20
Maintenance
13/20
Documentation
14/20
Setup experience
13/20
Why each score
Reliability 9/20
The manifest declares a single stdio transport, npm package @ask-llm/[email protected], and four optional env vars (default model alias, fallback model, timeout, log level). Its name io.github.Lykhoyda/ask-claude and description of read-only second opinions match the README's ask-claude entry (Opus with Sonnet fallback, native sessions, Read/Glob/Grep-only workspace access), so there is no visible contradiction between declared scope and described behavior. However, the supplied source material contains only server.json and the README; it includes no source code for packages/claude-mcp, no committed tests, and no per-package CI workflow, so the MCP init + tool-list handshake, error surfaces, and failure paths (missing CLI, unauthenticated CLI, the default 600000 ms timeout, model fallback) cannot be verified as controlled and diagnosable. Per the static calibration, reliability must not exceed 12 without verifiable execution evidence; scored 9, with deductions for absent committed tests/run evidence for this server and for an external runtime dependency (Claude Code CLI) whose presence and auth state cannot be confirmed statically.
Security and permissions 13/20
By description this server only produces read-only second opinions, and the README states ask-claude is limited to Read/Glob/Grep-level workspace access. All env vars in the manifest are marked isSecret=false and no API key or token is involved; install examples contain no real secrets. No malware, credential theft, covert exfiltration, fabricated identity/claims, or irreversible delete/pay/deploy/remote-command defaults appear, so no red-line trigger applies and the score is not in the 0-4 range. The notable residual risk is data flow: prompts and any workspace files read are passed through the local Claude Code CLI to a remote Anthropic model, a boundary only implied by README prose rather than demonstrated by server-level permission declarations, confirmation prompts, or scoping controls in the provided files; the 10-minute default timeout and override-able model alias are controllable but noteworthy. Scored 13; deductions for relying on README-level (not code-level) disclosure of the outbound data boundary and for the absence of a least-privilege declaration or explicit confirmation evidence for this package.
Maintenance 13/20
Evidence shows the repository is not archived, is MIT-licensed, and the README carries CI and release badges, version numbers, an explicit issues entry point, and CONTRIBUTING guidance, indicating release and contribution processes exist. The manifest version 0.0.1 matches the package version, giving basic versioning consistency. Gaps remain: commit cadence, issue responsiveness, and dependency-update practice for this server cannot be confirmed from the supplied material, the version is still early (0.0.1), and no security-response channel (e.g., SECURITY.md or a reporting path) is provided. Scored 13, deducting for early-stage versioning, no security-response channel evidence, and unverifiable issue/dependency maintenance rather than assuming the best case.
Documentation 14/20
The README is comparatively layered: it separates the unified server from per-provider packages, provides a package mapping table, multi-client configuration examples (Claude Code, Cursor, Codex CLI, Claude Desktop, Pi, generic STDIO), provider auth prerequisites, per-provider default and fallback models, and explicit disclosure of constraints such as the Gemini CLI enterprise gate; it also points to a docs site and llms.txt. For this server specifically it states the intended use (an independent Claude opinion from a non-Claude host) and the read-only workspace-tool boundary. Deductions: there is no per-parameter documentation for ask-claude (sessionId semantics, AskResponse/outputSchema fields, exact failure return shapes), troubleshooting is delegated to an external docs site that cannot be verified from the static material, and env-var coverage is manifest-level only. Scored 14 rather than higher.
Setup experience 13/20
The install path is clear and short: npx -y @ask-llm/claude-mcp (or codex mcp add claude -- npx -y @ask-llm/claude-mcp), with a Codex CLI TOML snippet and a generic STDIO JSON snippet, prerequisites being Node.js 20+ plus an installed and authenticated Claude Code CLI. This is a directly reusable configuration form for mainstream clients. Deductions: Linux/macOS only (README explicitly excludes Windows), a mandatory extra manual step of installing and authenticating the external Claude Code CLI, env vars to configure (though defaulted), and no concrete troubleshooting steps for typical failures (CLI absent/unauthenticated, model overload). Per the static calibration, setup must not exceed 15 without verifiable execution evidence for this package; scored 13.

Static review · not runReviewed 2026-09-25

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesRuns commands or codeUses the network

Best for

  • Developers whose primary assistant is Codex, Cursor, or another non-Claude client and who want an independent Claude opinion
  • Read-only, auditable code-review flows (Read/Glob/Grep access only)
  • Users who want to keep context in one session and ask follow-up questions

Not for

  • Scenarios where Claude must edit or write to the codebase
  • Users who want one registration covering all providers (Codex, Grok, Gemini, and so on) — use the unified @ask-llm/mcp package from the same repository
  • Users unwilling to install and authenticate the Claude Code CLI
  • Teams needing official Anthropic support or enterprise guarantees

Required permissions

  • Runs locally over stdio and invokes the installed, authenticated Claude Code CLI as a subprocess
  • Read-only workspace access limited to Read, Glob, and Grep
  • Reads the configured environment variables (model alias, fallback model, timeout, log level)
  • Sends prompts and relevant file contents to Claude

Risks and side effects

  • Prompts and file contents leave the machine and are processed by Claude, so sensitive code or secrets need care
  • Automatically invokes the Claude Code CLI, which may consume subscription or API quota
  • The default opus model falls back to sonnet when overloaded, so results may come from a different model than expected
  • Third-party, unofficial project with no affiliation with or endorsement by Anthropic
  • Version 0.0.1, so interfaces and behavior may change
  • get-usage-stats is in-memory only; stats are lost when the process restarts

Setup

Before you start

Runtime:Node.js 20+

Other optional settings (4)
ASK_CLAUDE_MODEL optional Default Claude model alias or full model name (default: opus); nothing to fetch, change it to pick another model.
ASK_CLAUDE_FALLBACK_MODEL optional Claude CLI fallback model used when the default is overloaded or unavailable (default: sonnet).
ASK_CLAUDE_TIMEOUT_MS optional Timeout for Claude CLI execution in milliseconds (default: 600000, i.e. 10 minutes).
GMCPT_LOG_LEVEL optional Log verbosity: debug, info, warn, error (default: warn).
  1. Install Node.js 20+ (Linux or macOS).
  2. Install and sign in to the Claude Code CLI (this server bridges to it for non-Claude clients).
  3. Register with your MCP client: for Codex CLI run codex mcp add claude -- npx -y @ask-llm/claude-mcp; for other clients add the STDIO config {"command":"npx","args":["-y","@ask-llm/claude-mcp"]}.
  4. Optional: set ASK_CLAUDE_MODEL (default opus), ASK_CLAUDE_FALLBACK_MODEL (default sonnet), ASK_CLAUDE_TIMEOUT_MS (default 600000 ms), GMCPT_LOG_LEVEL (default warn).
  5. Verify with the ping tool or by asking your assistant to "ask claude for an independent opinion".
.mcp.json
{
  "mcpServers": {
    "claude": {
      "command": "npx",
      "args": ["-y", "@ask-llm/claude-mcp"],
      "env": {
        "ASK_CLAUDE_MODEL": "opus",
        "ASK_CLAUDE_FALLBACK_MODEL": "sonnet",
        "ASK_CLAUDE_TIMEOUT_MS": "600000",
        "GMCPT_LOG_LEVEL": "warn"
      }
    }
  }
}

Shown for Claude Code. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "claude": {
      "command": "npx",
      "args": [
        "-y",
        "@ask-llm/claude-mcp"
      ],
      "env": {
        "ASK_CLAUDE_MODEL": "opus",
        "ASK_CLAUDE_FALLBACK_MODEL": "sonnet",
        "ASK_CLAUDE_TIMEOUT_MS": "600000",
        "GMCPT_LOG_LEVEL": "warn"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add claude -e ASK_CLAUDE_MODEL=opus -e ASK_CLAUDE_FALLBACK_MODEL=sonnet -e ASK_CLAUDE_TIMEOUT_MS=600000 -e GMCPT_LOG_LEVEL=warn -- npx -y @ask-llm/claude-mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Check that it works

The client's tool list should show ask-claude, get-usage-stats and ping; a prompt like "ask Claude for an independent opinion on this code" that returns a Claude response confirms the connection works.

Troubleshooting

  1. Use the ping tool first to confirm the MCP connection works
  2. Confirm the Claude Code CLI is installed and signed in, and that PATH resolves the command
  3. Check that ASK_CLAUDE_MODEL / ASK_CLAUDE_FALLBACK_MODEL are valid aliases and that the timeout is not too short
  4. Set GMCPT_LOG_LEVEL to debug or info for detailed logs if output looks wrong
  5. Confirm Node.js 20+ and the package name @ask-llm/claude-mcp (the old name @anton-lykhoyda/ask-claude-mcp is deprecated)
  6. Verify the client config uses the stdio transport with correct command and argument spelling

Things to try

Once connected, you can ask your AI assistant things like:

  • Ask Claude for an independent opinion on the changes in src/auth.ts
  • Ask Claude to review my last commit touching src/auth.ts
  • Ask Claude to debate the plan in docs/design.md
  • Show me the usage stats for this session

Tools 3

ask-claude read-only
Ask Claude for a read-only second opinion through the Claude Code CLI; defaults to opus with a sonnet fallback, supports native sessions, and has Read/Glob/Grep-only workspace access.
get-usage-stats read-only
Returns per-session token totals, fallback counts, and breakdowns by provider/model; kept in memory only.
ping read-only
Connection test tool.

Use cases

Have Codex or another non-Claude client request an independent Claude code review and second opinion
Debate or critique an architecture proposal or design document with Claude
Re-check a diff with a second model before committing, to catch what the first model missed
Let Claude read relevant files in a read-only workspace before answering

Supported clients

Claude Code
Codex
Cursor
Claude Desktop

Listed from the project's documentation, not tested by this site.

Overview

This is the server defined by packages/claude-mcp/server.json in the Ask LLM repository (npm package @ask-llm/claude-mcp). It bridges Codex and other MCP clients with the Anthropic Claude Code CLI so a non-Claude assistant can request read-only second opinions and code reviews. It runs over stdio and exposes the ask-claude, ping, and get-usage-stats tools; ask-claude defaults to the opus model with a sonnet fallback and grants read-only Read/Glob/Grep workspace access. It fits workflows where a non-Claude primary assistant (for example Codex) wants Claude's independent take on a diff, plan, or approach before committing. It is not for cases where Claude must write or modify files, and it is not the unified multi-provider orchestrator from the same repository (@ask-llm/mcp). It requires a separately installed and authenticated Claude Code CLI, and it is an unofficial third-party tool.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.4k · Tools 2 Compare with this →

Data synced 2026-09-25 Read the FMRS scoring method