create_signal_monitor — Nock MCP Tool Mutating
create_signal_monitor
(create signal monitor) is one of 99 tools on the
Nock
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call create_signal_monitor from your client
- Claude Code Nock create_signal_monitor run in your project directory
- Claude Desktop Nock create_signal_monitor ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nock create_signal_monitor ~/.cursor/mcp.json
- VS Code Nock create_signal_monitor .vscode/mcp.json
- Zed Nock create_signal_monitor ~/.config/zed/settings.json
- Windsurf Nock create_signal_monitor ~/.codeium/windsurf/mcp_config.json
- Cline Nock create_signal_monitor ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nock create_signal_monitor ~/.gemini/settings.json
- Grok Nock create_signal_monitor .mcp.json (in your project root)
- ChatGPT Nock create_signal_monitor Settings → Connectors → Advanced → Developer mode
- Claude.ai Nock create_signal_monitor Settings → Connectors → Add custom connector
- LangChain Nock create_signal_monitor pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nock https://api.usenock.com/mcpOther tools on this server
- create_sheet
- list_sheets
- get_sheet_rows
- qualify_sheet_leads
- add_rows_to_sheet
- add_enrichment_to_sheet
- discover_decision_makers
- identify_business
- confirm_decision_maker
- check_whatsapp
- find_companies_with_rules
- company_group
- company_products
- feed_campaign_with_signal
- import_linkedin_connections
- phone_owner
- clean_phone
- edit_sheet
- select_sheet_rows
- export_sheet_csv
- run_sheet_enrichment
- run_sheet_ai_column
- search_people
- search_companies
- list_enrichment_fields
- enrich_field
- enrich_field_batch
- research_web
- send_to_webhook
- ai_column
- list_outreach_templates
- save_outreach_template
- delete_outreach_template
- list_outreach_campaigns
- list_outreach_senders
- create_outreach_campaign
- generate_outreach_campaign
- update_outreach_campaign
- set_campaign_daily_people
- find_people_for_campaign
- set_campaign_signal_monitor
- update_outreach_cadence
- regenerate_outreach_cadence
- adjust_outreach_cadence
- update_cadence_ai_field
- list_cadence_versions
- restore_cadence_version
- preview_campaign_messages
- rewrite_campaign_messages
- add_prospects_to_campaign
- activate_outreach_campaign
- update_outreach_campaign_status
- list_prospects
- get_prospect
- update_prospect
- delete_prospect
- disqualify_prospect
- set_prospect_closure_reason
- activate_prospect_channel
- send_prospect_step_now
- brief_lead
- find_lead
- list_inbox_conversations
- get_inbox_conversation
- approve_inbox_message
- motor_report
- explore_signals
- list_signal_monitors
- update_signal_monitor
- run_signal_monitor
- list_signal_events
- export_signal_events
- list_received_invitations
- accept_received_invitation
- update_campaign_settings
- read_learn_article
- get_customer_list
- update_customer_list
- get_knowledge_base
- update_knowledge_base
- add_knowledge_document
- remove_knowledge_document
- add_cadence_rule
- remove_cadence_rule
- brain_lookup
- save_memory
- forget_memory
- create_routine
- list_routines
- set_routine_status
- delete_routine
- set_autonomy_level
- rename_sheet
- duplicate_sheet
- delete_sheet
- restore_company_sheet
- get_credit_balance
- send_feedback
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.