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