whats_the_signal — Antevo Executive Brief MCP Prompt

whats_the_signal is one of 5 prompts on the Antevo Executive Brief MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke whats_the_signal from your client

• Claude Code Antevo Executive Brief Prompt/whats_the_signal run in your project directory
• Claude Desktop Antevo Executive Brief Prompt/whats_the_signal ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Antevo Executive Brief Prompt/whats_the_signal ~/.cursor/mcp.json
• VS Code Antevo Executive Brief Prompt/whats_the_signal .vscode/mcp.json
• Zed Antevo Executive Brief Prompt/whats_the_signal ~/.config/zed/settings.json
• Windsurf Antevo Executive Brief Prompt/whats_the_signal ~/.codeium/windsurf/mcp_config.json
• Cline Antevo Executive Brief Prompt/whats_the_signal ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Antevo Executive Brief Prompt/whats_the_signal ~/.gemini/settings.json
• Grok Antevo Executive Brief Prompt/whats_the_signal .mcp.json (in your project root)
• ChatGPT Antevo Executive Brief Prompt/whats_the_signal Settings → Connectors → Advanced → Developer mode
• Claude.ai Antevo Executive Brief Prompt/whats_the_signal Settings → Connectors → Add custom connector
• LangChain Antevo Executive Brief Prompt/whats_the_signal pip install langchain-mcp-adapters

Other prompts on this server

• what_could_go_wrong
• whats_changed
• explain_this_move
• brief_me

Antevo Executive Brief also offers 1 resource — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.