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