audit_my_server — OpenApps MCP Prompt
audit_my_server
is one of 3 prompts on the
OpenApps
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke audit_my_server from your client
- Claude Code OpenApps Prompt/audit_my_server run in your project directory
- Claude Desktop OpenApps Prompt/audit_my_server ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor OpenApps Prompt/audit_my_server ~/.cursor/mcp.json
- VS Code OpenApps Prompt/audit_my_server .vscode/mcp.json
- Zed OpenApps Prompt/audit_my_server ~/.config/zed/settings.json
- Windsurf OpenApps Prompt/audit_my_server ~/.codeium/windsurf/mcp_config.json
- Cline OpenApps Prompt/audit_my_server ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI OpenApps Prompt/audit_my_server ~/.gemini/settings.json
- Grok OpenApps Prompt/audit_my_server .mcp.json (in your project root)
- ChatGPT OpenApps Prompt/audit_my_server Settings → Connectors → Advanced → Developer mode
- Claude.ai OpenApps Prompt/audit_my_server Settings → Connectors → Add custom connector
- LangChain OpenApps Prompt/audit_my_server pip install langchain-mcp-adapters
Other prompts on this server
OpenApps also offers 1 resource — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 14 November 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.