get_startup_signal — GitDealFlow MCP Tool Read-only
get_startup_signal
(get startup signal) is one of 4 tools on the
GitDealFlow
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_startup_signal from your client
- Claude Code GitDealFlow get_startup_signal run in your project directory
- Claude Desktop GitDealFlow get_startup_signal ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GitDealFlow get_startup_signal ~/.cursor/mcp.json
- VS Code GitDealFlow get_startup_signal .vscode/mcp.json
- Zed GitDealFlow get_startup_signal ~/.config/zed/settings.json
- Windsurf GitDealFlow get_startup_signal ~/.codeium/windsurf/mcp_config.json
- Cline GitDealFlow get_startup_signal ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GitDealFlow get_startup_signal ~/.gemini/settings.json
- Grok GitDealFlow get_startup_signal .mcp.json (in your project root)
- ChatGPT GitDealFlow get_startup_signal Settings → Connectors → Advanced → Developer mode
- Claude.ai GitDealFlow get_startup_signal Settings → Connectors → Add custom connector
- LangChain GitDealFlow get_startup_signal pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http gitdealflow https://gitdealflow.com/api/mcpOther tools on this server
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.