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