answer_google_review_match — Sergio by Serviche MCP Tool
answer_google_review_match
(answer google review match) is one of 111 tools on the
Sergio by Serviche
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call answer_google_review_match from your client
- Claude Code Sergio by Serviche answer_google_review_match run in your project directory
- Claude Desktop Sergio by Serviche answer_google_review_match ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sergio by Serviche answer_google_review_match ~/.cursor/mcp.json
- VS Code Sergio by Serviche answer_google_review_match .vscode/mcp.json
- Zed Sergio by Serviche answer_google_review_match ~/.config/zed/settings.json
- Windsurf Sergio by Serviche answer_google_review_match ~/.codeium/windsurf/mcp_config.json
- Cline Sergio by Serviche answer_google_review_match ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sergio by Serviche answer_google_review_match ~/.gemini/settings.json
- Grok Sergio by Serviche answer_google_review_match .mcp.json (in your project root)
- ChatGPT Sergio by Serviche answer_google_review_match Settings → Connectors → Advanced → Developer mode
- Claude.ai Sergio by Serviche answer_google_review_match Settings → Connectors → Add custom connector
- LangChain Sergio by Serviche answer_google_review_match pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sergio https://sergio.serviche.com/api/agent/mcp
Other tools on this server
- whoami
- catalog
- report_feedback
- events_subscribe
- events_list
- events_ack
- read
- query
- findClientByIdentifier
- send_text
- start_group_text
- open_conversation_by_phone
- assign_conversation
- set_conversation_status
- bulk_clear_conversations
- snooze_conversation
- unsnooze_conversation
- set_conversation_reminder
- dismiss_conversation_reminders
- link_conversation_to_client
- merge_conversations
- track_conversation_as_lead
- disposition_conversation
- start_conversation_flow
- close_conversation_flow
- remove_conversation_flow
- edit_draft
- send_email
- create_draft
- redraft_lead_step
- set_lead_outcome
- move_lead_journey
- hold_follow_ups
- hold_lead_follow_ups
- edit_lead_step
- update_payroll_settings
- add_staff_member
- edit_staff_member
- clear_staff_availability_override
- set_staff_weekly_hours
- record_staff_event
- add_staff_scheduling_rule
- remove_staff_scheduling_rule
- review_cleaner_roster
- edit_contacts
- accept_smaller_sync
- upload_spreadsheet
- start_spreadsheet_import
- review_import_mapping
- set_scanner_on
- create_scanner
- edit_scanner
- delete_scanner
- create_contact_list
- edit_contact_list
- create_contact_tag
- edit_contact_tag
- create_campaign
- edit_campaign
- delete_campaign
- start_campaign
- send_campaign_messages
- start_history_import
- cancel_import
- record_tools_access
- declare_lead_sources
- approve_follow_up_style
- set_flow_archived
- set_flow_on
- edit_flow
- set_staff_availability
- create_task
- complete_task
- skip_task
- reopen_task
- snooze_task
- assign_task
- update_task
- delete_task
- complete_tasks_bulk
- accept_suggestion
- dismiss_suggestion
- run_suggestion_now
- dismiss_notification
- create_client
- read_company_document
- decide_company_document_suggestion
- edit_client
- add_client_note
- log_call
- pin_client_note
- delete_client_note
- set_handbook_toolshed_sharing
- create_handbook_article
- edit_handbook_article
- archive_handbook_article
- draft_handbook_edit
- review_handbook_edit
- log_handbook_question
- answer_handbook_question
- create_training_module
- edit_training_module
- archive_training_module
- generate_training_questions
- add_training_question
- edit_training_question
- delete_training_question
- remove_training_assignment
- update_settings
- set_flow_start
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.