Kujo Workflows — Kujolang.ai MCP MCP Resource
Kujo Workflows
is one of 6 resources on the
Kujolang.ai MCP
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Kujo Workflows from your client
- Claude Code Kujolang.ai MCP Resource/Kujo Workflows run in your project directory
- Claude Desktop Kujolang.ai MCP Resource/Kujo Workflows ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Kujolang.ai MCP Resource/Kujo Workflows ~/.cursor/mcp.json
- VS Code Kujolang.ai MCP Resource/Kujo Workflows .vscode/mcp.json
- Zed Kujolang.ai MCP Resource/Kujo Workflows ~/.config/zed/settings.json
- Windsurf Kujolang.ai MCP Resource/Kujo Workflows ~/.codeium/windsurf/mcp_config.json
- Cline Kujolang.ai MCP Resource/Kujo Workflows ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Kujolang.ai MCP Resource/Kujo Workflows ~/.gemini/settings.json
- Grok Kujolang.ai MCP Resource/Kujo Workflows .mcp.json (in your project root)
- ChatGPT Kujolang.ai MCP Resource/Kujo Workflows Settings → Connectors → Advanced → Developer mode
- Claude.ai Kujolang.ai MCP Resource/Kujo Workflows Settings → Connectors → Add custom connector
- LangChain Kujolang.ai MCP Resource/Kujo Workflows pip install langchain-mcp-adapters
Other resources on this server
Kujolang.ai MCP also offers 3 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 30 September 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.