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