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