# OpenAI Codex CLI MCP

The Aikido MCP Plugin connects Aikido’s security engine to AI coding tools. It automatically scans AI generated code for vulnerabilities and hardcoded secrets as soon as it is created.

AI assistants can review their own output, but that review is not perfect. Aikido adds a reliable and consistent security layer that checks every generated snippet with proven scanning rules.

**Why use Aikido MCP**

* Deterministic, independent security checks on every AI generated snippet before it is committed
* Immediate detection and remediation of vulnerabilities and hardcoded secrets in AI assisted workflows
* Real time feedback, making AI driven development safer by default
* **aikido\_full\_scan**: Scans local code files for vulnerabilities (SAST) and hardcoded secrets.
* **aikido\_issues\_list**: Fetches security issues from your Aikido feed.
  * **Filter by one scope:** repo\_name, cloud\_name, vm\_name, domain\_name, or container\_name
  * **Pick one or more issue types:** sast, leaked\_secret, iac, open\_source, cloud, cloud\_instance, docker\_container, malware, eol, mobile, surface\_monitoring, scm\_security, license, ai\_pentest
  * **Returns each issue** with title, type, severity, and remediation steps

## Installation

{% stepper %}
{% step %}
**Create a personal access token**

In Aikido, go to [Settings → Integrations → IDE → MCP](https://app.aikido.dev/settings/integrations/ide/mcp)

Create a Personal Access Token.
{% endstep %}

{% step %}
**Install the Aikido MCP server**

```shellscript
codex mcp add aikido \
  --env AIKIDO_API_KEY=YOUR_TOKEN \
  -- npx -y @aikidosec/mcp
```

Replace `YOUR_TOKEN` with the token from the previous step.
{% endstep %}

{% step %}
**Add the Aikido rule to Global AGENTS file**

Create the codex directory if it doesn't exist yet.

```shellscript
mkdir -p ~/.codex/skills
```

Download the Aikido rule and add it to `~/.codex/skills/aikido-rule.txt`.

```shellscript
curl -fsSL "https://gist.githubusercontent.com/kidk/aa48cad6db80ba4a38493016aae67712/raw/3644397b7df43423e3da06434491b40bbb79dd47/aikido-rule.txt" \
  -o ~/.codex/skills/aikido-rule.txt
```

{% endstep %}

{% step %}
**Finished**

Aikido MCP is now available in Codex CLI.

{% hint style="info" %}
Restart Codex CLI if it was open.
{% endhint %}
{% endstep %}
{% endstepper %}

**Scanning code**

* "Use Aikido to scan this file for security issues"
* "Run an Aikido scan on my staged changes to check for secrets before I commit"
* "Scan the files I just edited with Aikido and link them to the `payments-api` repo"

**Reviewing issues by repo**

* "Show me all critical Aikido issues in `payments-api`"
* "List any leaked secrets in `frontend-web` from Aikido"
* "What open source vulnerabilities does Aikido see in `api-gateway`?"
* "Show SAST and IaC issues in `infra-core` from Aikido"

**Reviewing issues by cloud, VM, or container**

* "List all Aikido cloud issues in `prod-aws`"
* "Show malware findings on `web-server-01` from Aikido"
* "What end-of-life software is running in the `nginx-proxy` container per Aikido?"
* "Show me surface monitoring issues for `example.com` in Aikido"

**Combined workflows**

* "Use Aikido to scan my current changes, then show existing critical issues in the same repo"
* "Check this PR with Aikido and compare against open SAST issues in the repo"


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.aikido.dev/ai-and-dev-tools/aikido-mcp/openai-codex-cli-mcp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.