perimeter-watch — Perimeter Watch MCP Resource

perimeter-watch is one of 1 resource on the Perimeter Watch MCP server. Connect the server and your client can attach it as context.

by client

How to attach perimeter-watch from your client

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

Read from the server itself, by connecting to it and calling resources/list on 24 September 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.