Skip to content

# llm-cli-gateway - local MCP gateway for coding-agent CLIs

$ llm-cli-gateway.dev --view <TAB>
█
llm-cli-gateway - local MCP gateway for coding-agent CLIs
Claude Code / Codex / Gemini / Grok / Mistral Vibe - durable async jobs - MIT
Paste this into your AI agent:
`Read https://llm-cli-gateway.dev/install.md and configure yourself to use llm-cli-gateway as an MCP server.`
View the install spec · Repository
or run manually
`npx -y llm-cli-gateway`
$ npx -y llm-cli-gateway
MCP server connected over stdio
> consensus_check({ models: ["claude", "codex", "gemini"], claim })
claude_request: accepts with caveat
codex_request: flags missing test
gemini_request: suggests smaller patch
result: disagreement summarized for review
> claude_request_async({ prompt, outputFormat: "stream-json" })
jobId: 1f0c9a2e-…
status: running
persisted: ~/.llm-cli-gateway/logs.db
> llm_job_result({ jobId })
complete - result recovered after gateway restart
API proxy
POST /v1/messages
model response
no native Claude Code session
no Codex CLI resume
no local provider CLI config
file and test access must be rebuilt
Good for hosted chat. Thin for local coding agents.
llm-cli-gateway
MCP tool call
claude_request keeps Claude Code semantics
codex_request uses real Codex sessions
gemini_request uses the installed Antigravity CLI (agy)
grok_request and mistral_request follow provider CLIs
One MCP surface, real local CLIs underneath.

A Model Context Protocol (MCP) gateway for running Claude Code, Codex, Gemini, Grok, and Mistral Vibe CLIs from one MCP endpoint, with durable async jobs, session continuity, cache-aware prompting, observability, and personal-appliance setup tooling.

Why developers try it: one local MCP endpoint for cross-LLM validation, multi-agent coding workflows, and repeatable assistant-led setup across five provider CLIs.

Current signals: CI and security workflows pass on main, OpenSSF Scorecard is published, OpenSSF Best Practices is passing, releases use Sigstore signing, and the package is MIT licensed.

claude_request-> Claude Code with sessions and MCP server selection
codex_request-> OpenAI Codex CLI with real resume IDs
*_request_async-> long-running jobs persisted to SQLite
consensus_check-> ask several models and inspect disagreement
session_create-> reusable provider sessions and worktree-aware flows
approval_list-> review approval decisions from one place

The gateway orchestrates local CLIs. It does not replace them.

Posture
CI Security CodeQL OpenSSF Scorecard OpenSSF Best Practices npm provenance Sigstore CODEOWNERS Dependabot MIT

Signal | Status | Why it matters
--- | --- | ---
Runtime | local stdio MCP | provider CLIs keep owning file access and session state
Async jobs | durable SQLite store | long calls can survive gateway restarts
Validation | cross-model tools | compare, red-team, second opinion, and consensus workflows
Release | npm provenance + Sigstore | published artifacts have supply-chain evidence
License | MIT | open source and installable without a hosted service

Integration
MCP clients npx -y llm-cli-gateway stdio server for Claude Desktop, Claude Code, Codex, Gemini, and other MCP clients
Provider CLIs claude / codex / agy / grok / vibe uses the tools and credentials you already installed locally
Registry io.github.verivus-oss/llm-cli-gateway published to the official MCP Registry