inspect_placement — LinkBunny Placement Checker MCP Tool Read-only
inspect_placement
(inspect placement) is one of 1 tool on the
LinkBunny Placement Checker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call inspect_placement from your client
- Claude Code LinkBunny Placement Checker inspect_placement run in your project directory
- Claude Desktop LinkBunny Placement Checker inspect_placement ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LinkBunny Placement Checker inspect_placement ~/.cursor/mcp.json
- VS Code LinkBunny Placement Checker inspect_placement .vscode/mcp.json
- Zed LinkBunny Placement Checker inspect_placement ~/.config/zed/settings.json
- Windsurf LinkBunny Placement Checker inspect_placement ~/.codeium/windsurf/mcp_config.json
- Cline LinkBunny Placement Checker inspect_placement ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LinkBunny Placement Checker inspect_placement ~/.gemini/settings.json
- Grok LinkBunny Placement Checker inspect_placement .mcp.json (in your project root)
- ChatGPT LinkBunny Placement Checker inspect_placement Settings → Connectors → Advanced → Developer mode
- Claude.ai LinkBunny Placement Checker inspect_placement Settings → Connectors → Add custom connector
- LangChain LinkBunny Placement Checker inspect_placement pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http placement-checker https://mcp.getlinkbunny.com/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 13 October 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.