Mmcp.market

AI CLI MCP server

by mkXultra·io.github.mkXultra/ai-cli-mcp·v2.24.0
No reviews yet

Run Claude, Codex, Gemini, Forge, and OpenCode CLIs through MCP with background jobs

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

27 stars678 downloads/wk

Reviews

Write one

Nobody has reviewed AI CLI yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

AI CLI tools (9, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • cleanup_processeswrite action

    Remove all completed and failed processes from the process list to free up memory.

  • doctor

    Check supported AI CLI binary availability and path resolution. Does not verify login state or terms acceptance.

  • get_result

    Get the current output and status of an AI agent process by PID. Defaults to a compact result shape; set verbose to true for full metadata and detailed parsed output.

  • kill_processwrite action

    Terminate a running AI agent process by PID.

  • list_processes

    List all running and completed AI agent processes. Returns a simple list with PID, agent type, and status for each process.

  • models

    List supported model names, model aliases, and dynamic backend discovery hints.

  • peek

    One-shot short observation window for running child agents. Returns only natural-language message events, and optionally normalized tool_call events, observed during this call; not a history API, not gapless streaming, and not stdout/stderr tailing. In v1, message extraction is supported for Codex, Claude, OpenCode, Gemini, and best-effort Forge Summary/Completed successfully lines. Forge tool cal

  • runwrite action

    AI Agent Runner: Starts a Claude, Codex, Gemini, Forge, or OpenCode CLI process in the background and returns a PID immediately. Use list_processes and get_result to monitor progress. • File ops: Create, read, (fuzzy) edit, move, copy, delete, list files, analyze/ocr images, file content analysis • Code: Generate / analyse / refactor / fix • Git: Stage ▸ commit ▸ push ▸ tag (any workflow) • Termin

  • wait

    Wait for multiple AI agent processes to complete and return their results. Defaults to compact result items; set verbose to true for full metadata and detailed parsed output.

Public scan report

scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it

no findings
  • Code scan22 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the AI CLI repository's README, as published. We do not edit it. Read it on GitHub

AI CLI MCP Server

🇯🇵 日本語のREADMEはこちら

📦 Package Migration Notice: This package was formerly @mkxultra/claude-code-mcp and has been renamed to ai-cli-mcp to reflect its expanded support for multiple AI CLI tools.

An MCP (Model Context Protocol) server that allows running AI CLI tools (Claude, Codex, Gemini, Forge, OpenCode, and Grok) in background processes with automatic permission handling.

Did you notice that Cursor sometimes struggles with complex, multi-step edits or operations? This server, with its powerful unified run tool, enables multiple AI agents to handle your coding tasks more effectively.

Demo

Overview

This MCP server provides tools that can be used by LLMs to interact with AI CLI tools. When integrated with MCP clients, it allows LLMs to:

  • Run Claude CLI with all permissions bypassed (using --dangerously-skip-permissions)
  • Execute Codex CLI with approvals and sandbox bypassed (using --dangerously-bypass-approvals-and-sandbox)
  • Execute Gemini models through Antigravity CLI (agy --print, stream-json, and --dangerously-skip-permissions)
  • Execute Forge CLI in non-interactive mode (using forge -C -p )
  • Execute Grok Build CLI headlessly with streaming-messages-json, automatic tool approval, and automatic updates disabled
  • Execute OpenCode in non-interactive JSON mode (using opencode run --format json --dir )
  • Support multiple AI models: Claude (sonnet, sonnet[1m], opus, opusplan, fable, haiku), Codex (gpt-6-astra, gpt-5.4, gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-luna, gpt-5.5, gpt-5.4-mini, gpt-5.3-codex, gpt-5.3-codex-spark, gpt-5.2), Gemini (gemini-3.8-flash-high/medium/low, gemini-3.7-flash-high/medium/low, gemini-3.6-flash-high/medium/low, gemini-3.1-pro-high/low), Forge (forge), Grok (grok, grok-4.6, grok-4.5), and OpenCode (opencode plus explicit oc- wrappers such as oc-openai/gpt-5.4)
  • Manage background processes with PID tracking
  • Parse and return structured outputs from both tools

Usage Example (Advanced Parallel Processing)

You can instruct your main agent to run multiple tasks in parallel like this:

Launch agents for the following 3 tasks using acm mcp run:

1. Refactor src/backend code using sonnet

2. Create unit tests for src/frontend using gpt-5.3-codex

3. Update docs in docs/ using gemini-3.1-pro-high

While they run, please update the TODO list. Once done, use the wait tool to wait for all completions and report the results together.

Usage Example (Context Caching & Sharing)

You can reuse heavy context (like large codebases) using session IDs to save costs while running multiple tasks.

1. First, use acm mcp run with opus to read all files in src/ and understand the project structure.

2. Use the wait tool to wait for completion and retrieve the session_id from the result.

3. Using that session_id, run the following two tasks in parallel with acm mcp run:

- Create refactoring proposals for src/utils using sonnet

- Add architecture documentation to README.md using gpt-5.3-codex

4. Finally, wait again to combine both results.

Benefits

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y ai-cli-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add ai-cli-mcp -- npx -y ai-cli-mcp
Add to Cursor

AI CLI: common questions

Is AI CLI MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the AI CLI safety report
How do I install AI CLI?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does AI CLI need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is AI CLI maintained?
The last commit was 4 days ago (2026-09-17). The latest release is v2.24.0.
What can I use instead of AI CLI?
Servers from other publishers that do the same job: Claudexor MCP server.

Alternatives to AI CLI

Same job from other publishers: the closest match first, then the best rated.

  • Claudexor
    Route coding work across Claude Code, Codex, Cursor, and OpenCode with shared context.
    A

More from mkXultra →