search — SeaWeb MCP Tool Read-only
search
(search) is one of 43 tools on the
SeaWeb
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search from your client
- Claude Code SeaWeb search run in your project directory
- Claude Desktop SeaWeb search ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SeaWeb search ~/.cursor/mcp.json
- VS Code SeaWeb search .vscode/mcp.json
- Zed SeaWeb search ~/.config/zed/settings.json
- Windsurf SeaWeb search ~/.codeium/windsurf/mcp_config.json
- Cline SeaWeb search ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SeaWeb search ~/.gemini/settings.json
- Grok SeaWeb search .mcp.json (in your project root)
- ChatGPT SeaWeb search Settings → Connectors → Advanced → Developer mode
- Claude.ai SeaWeb search Settings → Connectors → Add custom connector
- LangChain SeaWeb search pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http seaweb https://api.seaweb.tech/mcp
Other tools on this server
- compare_search
- vote_comparison
- search_restaurants
- search_salons
- filter_restaurants
- filter_salons
- list_sources
- get_disruptions
- get_camera_visibility
- get_spot_conditions
- search_web
- research
- research_status
- build_dataset
- agent_job_status
- cancel_agent_job
- extract_url
- get_restaurant
- get_menu
- submit_feedback
- remember
- recall
- log_outcome
- get_site_skill
- get_salon
- get_services
- get_hours
- teamwork_preview
- get_entity
- get_details
- list_verticals
- search_destination_sentiment
- register_standing_query
- list_standing_queries
- delete_standing_query
- list_disruption_events
- get_disruption_event
- register_disruption_webhook
- list_disruption_webhooks
- delete_disruption_webhook
- resolve_geo
- travel_health
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.