Codex Security Cloud MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_security_metadataC | List accessible Codex Security Cloud repositories and author filters. |
| list_findingsC | List Codex Security Cloud findings in the open or closed section with filters. |
| get_findingA | Fetch one Codex Security Cloud finding. Compact by default; opt into generated patch diff or deeper evidence only when needed. |
| close_findingB | Close a Codex Security Cloud finding as fixed, won't fix, duplicate, or false positive. |
| reopen_findingC | Reopen a closed Codex Security Cloud finding. |
| request_site_prA | Ask Codex Security Cloud to generate its site-side patch/PR workflow for a finding. |
| apply_generated_patchA | Apply an already-generated Codex Security Cloud patch to a local git repo, commit it, and optionally close the finding as fixed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action (listing, fetching, closing, reopening, applying patches, requesting PRs, listing metadata) with no overlapping purposes, making agent selection unambiguous.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_findings, close_finding), providing predictable and readable naming.
Seven tools is well-scoped for a security findings server, covering essential operations without being too few (each tool has a clear role) or too many (no redundancy).
The tool set covers the full finding lifecycle: list, get, close, reopen, apply patch, and request site-side PR. Missing creation is natural (findings generated by system), and no dead ends exist.