set_follow_up — YouSpot MCP Tool Mutating
set_follow_up
(set follow up) is one of 112 tools on the
YouSpot
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call set_follow_up from your client
- Claude Code YouSpot set_follow_up run in your project directory
- Claude Desktop YouSpot set_follow_up ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor YouSpot set_follow_up ~/.cursor/mcp.json
- VS Code YouSpot set_follow_up .vscode/mcp.json
- Zed YouSpot set_follow_up ~/.config/zed/settings.json
- Windsurf YouSpot set_follow_up ~/.codeium/windsurf/mcp_config.json
- Cline YouSpot set_follow_up ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI YouSpot set_follow_up ~/.gemini/settings.json
- Grok YouSpot set_follow_up .mcp.json (in your project root)
- ChatGPT YouSpot set_follow_up Settings → Connectors → Advanced → Developer mode
- Claude.ai YouSpot set_follow_up Settings → Connectors → Add custom connector
- LangChain YouSpot set_follow_up pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http youspot https://youspot.com/mcp/v1
Other tools on this server
- what_needs_attention
- get_my_plan
- draft_cloud_agent
- research_company
- company_signals
- get_domain_info
- get_domain_value
- send_email
- read_file
- save_file_from_url
- import_contacts_from_file
- search_gmail_messages
- get_gmail_message
- list_gmail_labels
- create_gmail_draft
- archive_gmail_message
- sent_contact_rule
- get_granola_notes
- get_granola_note
- search_granola_transcripts
- get_granola_status
- sync_granola_notes
- get_calendar_events
- list_google_calendars
- create_calendar_event
- update_calendar_event
- list_graph_objects
- get_graph_object
- set_graph_object_fields
- search_graph_objects
- create_graph_object
- create_tracker
- connect_graph_objects
- delete_graph_object
- delete_graph_objects
- record_interaction
- audit_brain
- merge_graph_objects
- unmerge_graph_objects
- purge_graph_object
- disconnect_graph_objects
- find_paths
- mutual_connections
- similar_objects
- query_graph_objects
- quiet_contacts
- referral_paths
- ask_about_hubspot_contacts
- ask_about_hubspot_companies
- get_hubspot_summary
- search_hubspot_crm
- list_integrations
- get_integration_connect_url
- disconnect_integration
- parse_invoice_pdf
- get_domain_keywords
- search_connections
- get_connection_details
- ask_about_connections
- ask_about_invitations
- get_connections_summary
- get_my_linkedin_posts
- linkedin_analytics
- get_messages_summary
- top_message_correspondents
- search_linkedin_posts
- analyze_recent_posts
- job_changes
- check_person_changes
- send_text_to_user
- list_scheduled_texts
- cancel_scheduled_text
- set_notification_emails
- list_obsidian_vaults
- search_obsidian_notes
- list_obsidian_notes
- get_obsidian_note
- update_my_profile
- find_companies
- search_slack_messages
- get_slack_thread
- list_slack_channels
- send_slack_message
- add_slack_reaction
- list_brand_kits
- get_brand_kit
- create_brand_kit
- update_brand_kit
- set_default_brand_kit
- extract_brand_kit
- generate_og_image
- generate_email
- generate_substack_post
- generate_markdown
- generate_pdf
- draft_email_in_gmail
- save_as_template
- list_templates
- plan_generation
- list_artifacts
- get_artifact
- read_artifact
- share_artifact
- get_my_tweets
- get_my_bookmarks
- get_twitter_profile
- get_twitter_following
- search_tweets
- read_web_page
- web_search
- check_page_changes
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.