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