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