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