Back to Browse

Ask Llm MCP Server

AI & MLLow Risk10.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

Bridge Claude with Gemini CLI for AI-to-AI collaboration, code review, and second opinions

About

Bridge Claude with Gemini CLI for AI-to-AI collaboration, code review, and second opinions

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. Trust signals: trusted author (7/7 approved); 4 highly-trusted packages. 1 finding(s) downgraded by scanner intelligence.

14 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

env_vars

Check that this permission is expected for this type of plugin.

Shell Command Execution

Runs commands on your machine. Be cautious — only use if you trust this plugin.

What You'll Need

Set these up before or after installing:

Timeout for Gemini CLI execution in milliseconds (default: 300000 = 5 minutes)Optional

Environment variable: GMCPT_TIMEOUT_MS

Log verbosity: debug, info, warn, error (default: warn)Optional

Environment variable: GMCPT_LOG_LEVEL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-lykhoyda-ask-gemini": {
      "env": {
        "GMCPT_LOG_LEVEL": "your-gmcpt-log-level-here",
        "GMCPT_TIMEOUT_MS": "your-gmcpt-timeout-ms-here"
      },
      "args": [
        "-y",
        "@ask-llm/gemini-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Ask LLM

Second opinions for coding agents.

Get a second opinion on your code or plan, inside your coding assistant, using the model subscriptions you already have.

For individual developers and small teams who already use a coding assistant and pay for another model subscription: ask a different vendor's model to review your changes or challenge your plan, without API keys, copy-paste, or leaving the session.

You:    ask codex to review src/auth.ts for security issues
Codex:  ⚠ verifyToken() compares tokens with === — not timing-safe (line 42)
        ⚠ the session cookie is missing a SameSite attribute
Claude: Good catches — applying both fixes to src/auth.ts.

Install

You need Node.js 24+ on Linux or macOS. Before your first review, both your coding assistant (for example Claude Code) and the provider you will consult (for example Codex) must be installed and signed in. Ask LLM configures the connection; it does not install providers or sign you in. If a provider CLI such as Codex has never been signed in on this machine, sign in first and rerun setup.

npm i -g @ask-llm/mcp && ask-llm setup

Setup asks you to confirm each detected host and workflow. Inspect the preview, confirm your assistant's registration and workflows, decline the others, then follow any printed manual steps. Restart your assistant or start a new session in your project.

Your first review

With both Claude Code and Codex installed and signed in, open Claude Code in your project and ask:

Ask Codex to review my staged changes for bugs and missing error handling. Check each finding against the source before proposing fixes.

Working in Codex with a Claude subscription? Ask Claude instead. Choose a provider from a different vendor than your current assistant. A successful review names the reviewer and model, cites relevant code, and reports findings or says it found none. Your assistant applies changes after you decide what to accept. If the request fails, run ask-llm doctor and follow the troubleshooting guide for your selected assistant and reviewer. Warnings about providers you do not use do not require installing them or adding API keys.

For plans, try: “Ask Claude to challenge this plan: what assumptions could fail, and what simpler approach would fit our constraints?”

After an on-demand review, pair review can add ongoing feedback. Pairing requires explicit opt-in; setup leaves it off.

Supported hosts

A host is the assistant you work in; a provider is the model you consult.

HostExperience
Claude CodeReviews, plan critique, comparisons; isolated reviewers and opt-in per-edit pairing
Codex, Cursor, Grok Build, Gemini CLITools and portable workflows; pairing on demand
AntigravityTools; setup prints a manual step for workflows
Pi 0.83.0+Native tools and portable workflows; opt-in per-edit pairing
Claude DesktopTools only
OpenCodeTools and portable workflows; setup verified with fixtures only

See host compatibility for the complete matrix and manual setup limits, including existing Codex registrations.

Supported providers

ProviderAccess
CodexYour authenticated Codex CLI/account
ClaudeYour authenticated Claude Code account; consult it from a host other than Claude Code
GrokAuthenticated Grok Build, an exact Cursor model, or the explicit metered xAI API option
AntigravityYour authenticated agy subscription; execution is off by default, and opt-in has no read-only guarantee
OllamaLocal models on your machine
GeminiAn eligible Gemini Code Assist Standard/Enterprise seat

Cursor Agent can also consult exact models from your Cursor catalog. It is a connection route, with usage governed by your Cursor plan.

Trust and cost

Review runs use read-only provider controls; the assistant you work in remains the editor. Antigravity refuses execution until explicitly enabled and cannot guarantee read-only access after opt-in. Review only material you are allowed to share with the selected provider.

Calls consume your existing provider plan's quota or follow that account's billing. Grok's xAI API is a separate, metered option requiring an API key; Ask LLM never enables billing or overage for you. Ollama supports local inference. Ask LLM sends no telemetry; provider and host data policies still apply.

Agreement between models is not proof of correctness. Validate findings against the code, tests, and your requirements. See data flow and costs and fallbacks.

Migrating from @ask-llm/*

Follow the migration guide before retiring earlier registrations.

Upgrade or remove · Troubleshooting · Documentation

Contributions: CONTRIBUTING.md. Licensed under MIT.

Reviews

No reviews yet

Be the first to review this server!