audit-report — KOB Live Restaurant Ops Audit MCP Resource
audit-report
is one of 1 resource on the
KOB Live Restaurant Ops Audit
MCP server. Connect the server and your client can attach it as context.
by client
How to attach audit-report from your client
- Claude Code KOB Live Restaurant Ops Audit Resource/audit-report run in your project directory
- Claude Desktop KOB Live Restaurant Ops Audit Resource/audit-report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor KOB Live Restaurant Ops Audit Resource/audit-report ~/.cursor/mcp.json
- VS Code KOB Live Restaurant Ops Audit Resource/audit-report .vscode/mcp.json
- Zed KOB Live Restaurant Ops Audit Resource/audit-report ~/.config/zed/settings.json
- Windsurf KOB Live Restaurant Ops Audit Resource/audit-report ~/.codeium/windsurf/mcp_config.json
- Cline KOB Live Restaurant Ops Audit Resource/audit-report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI KOB Live Restaurant Ops Audit Resource/audit-report ~/.gemini/settings.json
- Grok KOB Live Restaurant Ops Audit Resource/audit-report .mcp.json (in your project root)
- ChatGPT KOB Live Restaurant Ops Audit Resource/audit-report Settings → Connectors → Advanced → Developer mode
- Claude.ai KOB Live Restaurant Ops Audit Resource/audit-report Settings → Connectors → Add custom connector
- LangChain KOB Live Restaurant Ops Audit Resource/audit-report pip install langchain-mcp-adapters
KOB Live Restaurant Ops Audit also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 8 October 2026.
A listing does not declare its resources, 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 resource's type and contents.