check_availability — Brick NJ Local directory MCP Tool Read-only
check_availability
(check availability) is one of 7 tools on the
Brick NJ Local directory
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_availability from your client
- Claude Code Brick NJ Local directory check_availability run in your project directory
- Claude Desktop Brick NJ Local directory check_availability ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Brick NJ Local directory check_availability ~/.cursor/mcp.json
- VS Code Brick NJ Local directory check_availability .vscode/mcp.json
- Zed Brick NJ Local directory check_availability ~/.config/zed/settings.json
- Windsurf Brick NJ Local directory check_availability ~/.codeium/windsurf/mcp_config.json
- Cline Brick NJ Local directory check_availability ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Brick NJ Local directory check_availability ~/.gemini/settings.json
- Grok Brick NJ Local directory check_availability .mcp.json (in your project root)
- ChatGPT Brick NJ Local directory check_availability Settings → Connectors → Advanced → Developer mode
- Claude.ai Brick NJ Local directory check_availability Settings → Connectors → Add custom connector
- LangChain Brick NJ Local directory check_availability pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http directory https://bricknjlocal.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.