compliance_readiness — AgentAegis MCP Prompt

compliance_readiness is one of 4 prompts on the AgentAegis MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke compliance_readiness from your client

• Claude Code AgentAegis Prompt/compliance_readiness run in your project directory
• Claude Desktop AgentAegis Prompt/compliance_readiness ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor AgentAegis Prompt/compliance_readiness ~/.cursor/mcp.json
• VS Code AgentAegis Prompt/compliance_readiness .vscode/mcp.json
• Zed AgentAegis Prompt/compliance_readiness ~/.config/zed/settings.json
• Windsurf AgentAegis Prompt/compliance_readiness ~/.codeium/windsurf/mcp_config.json
• Cline AgentAegis Prompt/compliance_readiness ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI AgentAegis Prompt/compliance_readiness ~/.gemini/settings.json
• Grok AgentAegis Prompt/compliance_readiness .mcp.json (in your project root)
• ChatGPT AgentAegis Prompt/compliance_readiness Settings → Connectors → Advanced → Developer mode
• Claude.ai AgentAegis Prompt/compliance_readiness Settings → Connectors → Add custom connector
• LangChain AgentAegis Prompt/compliance_readiness pip install langchain-mcp-adapters

Other prompts on this server

• security_audit
• pre_install_trust_check
• incident_response

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.