codex_mcp_server_ebka

gustavorobertux/codex_mcp_server_ebka

3.2

If you are the rightful owner of codex_mcp_server_ebka and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.

The Codex MCP Server for Ebka Caido Plugin is a specialized server setup that allows seamless interaction between Codex CLI and the Ebka Caido plugin, facilitating advanced plugin management and operations.

Codex MCP Server for Ebka Caido Plugin

This folder mirrors the original Claude MCP server, but is packaged and documented specifically for the Codex CLI so you can talk to the Ebka Caido plugin from Codex sessions.

Requirements

  • Node.js 16+
  • Access to the Caido instance that has the Ebka plugin installed

Install & Build

cd codex-mcp-server
npm install
npm run build

Registering the server with Codex

  1. Open the Codex configuration file:
    • Linux/macOS: code ~/.codex/config.toml
    • Windows (PowerShell): code $env:USERPROFILE\\.codex\\config.toml
  2. Add a new MCP server entry that points to the compiled script:
[mcp_servers.caido]
command = "node"
args = ["/absolute/path/to/codex-mcp-server/build/index.js"]

Replace the path above with your real build directory. When running Codex, this server will now be available alongside any other MCP integrations you have configured.

Using from Codex

  1. Start a Codex session (e.g. codex from your terminal inside the Caido project).
  2. Ask Codex to connect to the caido MCP server.
  3. Immediately call the sendAuthToken tool with the auth_token and api_endpoint copied from the Ebka plugin inside Caido. This primes the server with credentials.
  4. After authentication, any of the remaining Ebka tools (HTTPQL queries, replay management, findings, etc.) can be invoked directly from Codex.

The implementation inside src/ is identical to the Claude version to keep parity with future plugin changes—only packaging and docs differ so Codex users have a dedicated entry point.