widget-result — Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor MCP Resource
widget-result
is one of 10 resources on the
Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor
MCP server. Connect the server and your client can attach it as context.
by client
How to attach widget-result from your client
- Claude Code Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor Resource/widget-result run in your project directory
- Claude Desktop Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor Resource/widget-result ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor Resource/widget-result ~/.cursor/mcp.json
- VS Code Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor Resource/widget-result .vscode/mcp.json
- Zed Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor Resource/widget-result ~/.config/zed/settings.json
- Windsurf Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor Resource/widget-result ~/.codeium/windsurf/mcp_config.json
- Cline Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor Resource/widget-result ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor Resource/widget-result ~/.gemini/settings.json
- Grok Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor Resource/widget-result .mcp.json (in your project root)
- ChatGPT Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor Resource/widget-result Settings → Connectors → Advanced → Developer mode
- Claude.ai Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor Resource/widget-result Settings → Connectors → Add custom connector
- LangChain Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor Resource/widget-result pip install langchain-mcp-adapters
Other resources on this server
Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor also offers 2 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 21 October 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.