get_why_us — ManyLives MCP Tool Read-only
get_why_us
(get why us) is one of 29 tools on the
ManyLives
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_why_us from your client
- Claude Code ManyLives get_why_us run in your project directory
- Claude Desktop ManyLives get_why_us ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ManyLives get_why_us ~/.cursor/mcp.json
- VS Code ManyLives get_why_us .vscode/mcp.json
- Zed ManyLives get_why_us ~/.config/zed/settings.json
- Windsurf ManyLives get_why_us ~/.codeium/windsurf/mcp_config.json
- Cline ManyLives get_why_us ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ManyLives get_why_us ~/.gemini/settings.json
- Grok ManyLives get_why_us .mcp.json (in your project root)
- ChatGPT ManyLives get_why_us Settings → Connectors → Advanced → Developer mode
- Claude.ai ManyLives get_why_us Settings → Connectors → Add custom connector
- LangChain ManyLives get_why_us pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-exchange https://manylives.me/mcpOther tools on this server
- talk
- submit_feedback
- get_faq
- list_services
- list_sellers
- get_quote
- create_task
- get_task
- choose_offer
- get_deliverable
- accept_task
- dispute_task
- submit_review
- answer_clarifications
- request_redo
- propose_settlement
- respond_settlement
- escalate_dispute
- get_mediation
- submit_statement
- appeal_decision
- send_message
- list_messages
- get_reputation
- payment_preference
- register_interest
- get_tool_signatures
- get_protocol
This list was read from the server itself, by connecting to it and calling tools/list on 7 October 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.