usage — Corrie Site Check MCP Resource
usage
is one of 2 resources on the
Corrie Site Check
MCP server. Connect the server and your client can attach it as context.
by client
How to attach usage from your client
- Claude Code Corrie Site Check Resource/usage run in your project directory
- Claude Desktop Corrie Site Check Resource/usage ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Corrie Site Check Resource/usage ~/.cursor/mcp.json
- VS Code Corrie Site Check Resource/usage .vscode/mcp.json
- Zed Corrie Site Check Resource/usage ~/.config/zed/settings.json
- Windsurf Corrie Site Check Resource/usage ~/.codeium/windsurf/mcp_config.json
- Cline Corrie Site Check Resource/usage ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Corrie Site Check Resource/usage ~/.gemini/settings.json
- Grok Corrie Site Check Resource/usage .mcp.json (in your project root)
- ChatGPT Corrie Site Check Resource/usage Settings → Connectors → Advanced → Developer mode
- Claude.ai Corrie Site Check Resource/usage Settings → Connectors → Add custom connector
- LangChain Corrie Site Check Resource/usage pip install langchain-mcp-adapters
Other resources on this server
Corrie Site Check 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 14 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.