codex_mcp_server_ebka

This MCP server enables Codex to communicate with the Ebka Caido plugin via the Codex CLI. It mirrors the Claude MCP server behavior but is packaged and documented for Codex sessions, providing tools to authenticate and perform Ebka-related operations such as HTTPQL queries, replay management, and findings retrieval. After wiring the server into Codex, you can start a Codex session and connect to the codex-mcp-server-ebka instance, then invoke the Ebka tools directly from Codex to interact with Caido's Ebka plugin.

To use it effectively, first authenticate the server by sending an auth token and the Ebka API endpoint using the sendAuthToken tool. Once authenticated, you can call remaining Ebka tools (e.g., HTTPQL queries, replay controls, and findings) directly from Codex in natural language prompts, with Codex translating your requests into Ebka-compatible API calls via this MCP server.

Prerequisites:

• Node.js 16+ installed on your machine
• Access to the Caido instance that has the Ebka plugin installed
• A Codex configuration ready to register an MCP server

Install and build the server:

# From your project root
cd codex-mcp-server
npm install
npm run build

Register the MCP server with Codex:

[mcp_servers.caido]
command = "node"
args = ["/absolute/path/to/codex-mcp-server/build/index.js"]

Replace /absolute/path/to/codex-mcp-server/build/index.js with the actual path to your built entry point. Save the configuration, then start Codex and connect to the caido MCP server entry. After that, you can invoke Ebka-related tools from Codex as described in the README.

Notes and tips:

• Ensure Node.js 16+ is installed and available on your PATH.
• The server expects to be pointed at the built index.js from the codex-mcp-server build output.
• When configuring Codex, provide the absolute path to the built entry and use the command set to node with the script path.
• The server uses the Ebka Caido plugin credentials; you must supply an auth_token and api_endpoint via the sendAuthToken tool before other Ebka operations.
• If you encounter path or permission issues, verify file permissions on build/index.js and that the path in Codex config is accessible by the Codex process.
• This MCP server mirrors Claude’s implementation for parity with future plugin changes, but packaging and docs are tailored for Codex users.