get_exit_capacity — YieldSignal MCP Tool Read-only
get_exit_capacity
(get exit capacity) 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_exit_capacity from your client
- Claude Code YieldSignal get_exit_capacity run in your project directory
- Claude Desktop YieldSignal get_exit_capacity ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor YieldSignal get_exit_capacity ~/.cursor/mcp.json
- VS Code YieldSignal get_exit_capacity .vscode/mcp.json
- Zed YieldSignal get_exit_capacity ~/.config/zed/settings.json
- Windsurf YieldSignal get_exit_capacity ~/.codeium/windsurf/mcp_config.json
- Cline YieldSignal get_exit_capacity ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI YieldSignal get_exit_capacity ~/.gemini/settings.json
- Grok YieldSignal get_exit_capacity .mcp.json (in your project root)
- ChatGPT YieldSignal get_exit_capacity Settings → Connectors → Advanced → Developer mode
- Claude.ai YieldSignal get_exit_capacity Settings → Connectors → Add custom connector
- LangChain YieldSignal get_exit_capacity 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.