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