Codex Security Cloud MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/obinnanwachukwu1/codex-security-cloud-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server