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