get_task_status — Lightbringer MCP Tool Read-only
get_task_status
(get task status) is one of 20 tools on the
Lightbringer
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_task_status from your client
- Claude Code Lightbringer get_task_status run in your project directory
- Claude Desktop Lightbringer get_task_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Lightbringer get_task_status ~/.cursor/mcp.json
- VS Code Lightbringer get_task_status .vscode/mcp.json
- Zed Lightbringer get_task_status ~/.config/zed/settings.json
- Windsurf Lightbringer get_task_status ~/.codeium/windsurf/mcp_config.json
- Cline Lightbringer get_task_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Lightbringer get_task_status ~/.gemini/settings.json
- Grok Lightbringer get_task_status .mcp.json (in your project root)
- ChatGPT Lightbringer get_task_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Lightbringer get_task_status Settings → Connectors → Add custom connector
- LangChain Lightbringer get_task_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http connector https://mcp.lightbringer.com/mcp
Other tools on this server
- whoami
- list_innovations
- get_innovation
- update_innovation
- request_patent_preparation
- get_innovation_template
- register_innovation
- search
- fetch
- list_tasks
- delete_task
- start_innovation_feedback
- send_developer_feedback
- list_reviews
- get_review
- respond_to_review
- add_comment
- add_discussion_comment
- reply_to_comment
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.