Prerequisites
Before you begin, ensure you have:- Python 3.10+ and Node.js 18+ installed
- Claude Code CLI (for bot channels and automation scripts)
- Cursor IDE (optional, for direct terminal usage)
This guide assumes you have a PropHero team account with access to ClickUp, Slack, and Google Workspace.
Installation
Configure environment variables
Copy the example environment file and fill in your values:Edit
.env and set:Configure MCPs
Set up your MCP integrations in
~/.cursor/mcp.json (for Cursor) or ~/.claude.json (for CLI):For complete MCP configuration instructions, see the MCP Setup guide.
Choose your channel
Claudio supports multiple interaction channels. Pick the one that fits your workflow:- Terminal (Cursor)
- Telegram
- Slack
- Web Dashboard
Best for: Direct usage during development
Verify MCP configuration
Ensure your
~/.cursor/mcp.json is configured with the MCPs from the previous step.Your first workflow
Let’s create a User Story in ClickUp using the ClickUp MCP integration:Claudio gathers context
Claudio will:
- Read the parent Initiative or Epic for context
- Use the User Story template from
docs/integrations/clickup/templates/ - Extract relevant information about the project
Task is created
Claudio will use the ClickUp MCP to create a task with:
- Title and description
- Acceptance criteria
- Technical notes
- Business value
- Assignment to the Sprint Backlog list
This workflow uses multiple tools:
get_workspace_hierarchy (context), get_task (parent info), and create_task (creation).Next steps
Explore workflows
Discover pre-built workflows for product management, sprint reporting, and automation
Configure integrations
Set up ClickUp, GitHub, Slack, Google Docs, and other MCP integrations
Learn the architecture
Understand how Claudio’s channels, brain, and MCPs work together
Secure your setup
Configure rate limiting, user authorization, and permissions
Common commands
Here are some common requests you can make to Claudio across any channel:- Product management: “Create an initiative for improving onboarding flow”
- Sprint planning: “Generate the sprint report for the current sprint”
- Code tasks: “Create a GitHub issue for the bug we just discussed”
- Communication: “Post a message in #engineering about today’s deployment”
- Data analysis: “Analyze the conversion funnel from the last 7 days”
- Meeting notes: “Find the meeting notes from yesterday’s standup”
Troubleshooting
MCP not found or connection error
MCP not found or connection error
Cause: The MCP server isn’t configured or credentials are invalid.Solution:
- Verify your MCP configuration in
~/.cursor/mcp.jsonor~/.claude.json - Check that all environment variables (API keys, tokens) are set correctly
- Restart Cursor or the bot to reload the configuration
- Test MCP health at
http://localhost:8000/api/mcps/health(web dashboard)
Permission denied errors
Permission denied errors
Cause:
SKIP_PERMISSIONS is not enabled or tool permissions are restricted.Solution:
Set in your .env:Bot not responding
Bot not responding
Cause: User not authorized, bot process crashed, or rate limit exceeded.Solution:
- Check that your user ID is in
ALLOWED_USER_IDS(Telegram) orSLACK_ALLOWED_USER_IDS(Slack) - Check bot logs in
channels/{telegram|slack}/orscripts/logs/ - Verify the bot process is running:
ps aux | grep bot.py - Restart the bot:
./channels/{channel}/start.sh
Command timeout
Command timeout
Cause: Task took longer than
COMMAND_TIMEOUT (default 30 minutes).Solution:
Increase the timeout in .env:Need help?
- Architecture: Learn how Claudio works at Architecture
- Channels: Detailed setup for Telegram, Slack, Web
- Integrations: Configure ClickUp, GitHub, Slack, Google Docs
- Configuration: Environment variables, Security, MCP setup