Skip to content

Document stdio for Mistral Vibe and Codex CLI - #181

Merged
jasperf merged 1 commit into
mainfrom
docs/mcp-mistral-stdio
Aug 6, 2026
Merged

Document stdio for Mistral Vibe and Codex CLI#181
jasperf merged 1 commit into
mainfrom
docs/mcp-mistral-stdio

Conversation

@jasperf

@jasperf jasperf commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

What

mcp-server/README.md implied Streamable HTTP was the transport non-Claude
clients (Mistral, others) need. That's wrong — stdio is a core MCP transport,
not Claude-specific, and Mistral Vibe CLI / OpenAI Codex CLI both support it
the same way Claude Code does: spawn mcp-server/run.sh locally, no token or
port needed.

Changes

  • Added "Register with Mistral Vibe" and "Register with OpenAI Codex CLI"
    sections, mirroring the existing "Register with Claude Code" one, each with
    the correct config.toml shape for that client (Mistral: [[mcp_servers]]
    array-of-tables; Codex: [mcp_servers.<name>] keyed table).
  • Reframed "Running as a network service (Streamable HTTP)" as for genuinely
    remote/shared-server cases only — not something a local Mistral/Codex/Claude
    CLI needs.
  • Noted OpenAI's server-side Responses API (unlike its Codex CLI) is
    remote-MCP-only and can't spawn a local process at all, so stdio guidance
    doesn't apply there.

All client-specific claims verified against each vendor's own current docs
(2026-08-06). Not yet verified end-to-end against a live Mistral Vibe or
Codex CLI install connecting to this server — flagged as such in the doc.

Version

Patch bump (5.1.3 → 5.1.4) — docs correction, no code/behavior change.

@jasperf
jasperf merged commit 510ed8e into main Aug 6, 2026
1 check passed
@jasperf
jasperf deleted the docs/mcp-mistral-stdio branch August 6, 2026 01:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant