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