Skip to main content
Get Claudio running and execute your first productivity workflow in minutes. This guide covers installation, MCP configuration, and usage across all channels.

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

1

Clone the repository

git clone https://github.com/cuba1511/claudio.git
cd claudio
2

Set up Python environment

python3 -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate
pip install -r requirements.txt
3

Configure environment variables

Copy the example environment file and fill in your values:
cp .env.example .env
Edit .env and set:
WORKSPACE_PATH=/path/to/claudio
CLAUDE_CLI_PATH=claude
ALLOWED_TOOLS=*
SKIP_PERMISSIONS=true
COMMAND_TIMEOUT=1800
See the Environment Configuration guide for detailed explanations of all variables.
4

Configure MCPs

Set up your MCP integrations in ~/.cursor/mcp.json (for Cursor) or ~/.claude.json (for CLI):
{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": ["-y", "@taazkareem/clickup-mcp-server@latest"],
      "env": {
        "CLICKUP_MCP_LICENSE_KEY": "your-license-key",
        "CLICKUP_API_KEY": "your-api-key",
        "CLICKUP_TEAM_ID": "your-team-id"
      }
    },
    "slack": {
      "command": "npx",
      "args": ["-y", "slack-mcp-server@latest", "--transport", "stdio"],
      "env": {
        "SLACK_MCP_XOXC_TOKEN": "xoxc-your-token",
        "SLACK_MCP_XOXD_TOKEN": "xoxd-your-token"
      }
    }
  }
}
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:
Best for: Direct usage during development
1

Open Cursor IDE

Open the Claudio project directory in Cursor:
cursor .
2

Verify MCP configuration

Ensure your ~/.cursor/mcp.json is configured with the MCPs from the previous step.
3

Restart Cursor

Restart Cursor to load the MCP configuration.
4

Start chatting

Open the Claude chat panel in Cursor and start asking Claudio to help you:
Create a user story in ClickUp for adding dark mode to the settings page

Your first workflow

Let’s create a User Story in ClickUp using the ClickUp MCP integration:
1

Start a conversation

Using your preferred channel (Terminal, Telegram, Slack, or Web), ask Claudio:
Create a user story for adding a password reset feature to the login page
2

Claudio gathers context

Claudio will:
  1. Read the parent Initiative or Epic for context
  2. Use the User Story template from docs/integrations/clickup/templates/
  3. Extract relevant information about the project
3

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
4

Get the link

Claudio responds with a link to the newly created ClickUp task:
✅ Created User Story: "Add password reset feature"
📎 https://app.clickup.com/t/901213056238/TASK-123

💡 Next: Review the task and assign it to a sprint
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

Cause: The MCP server isn’t configured or credentials are invalid.Solution:
  1. Verify your MCP configuration in ~/.cursor/mcp.json or ~/.claude.json
  2. Check that all environment variables (API keys, tokens) are set correctly
  3. Restart Cursor or the bot to reload the configuration
  4. Test MCP health at http://localhost:8000/api/mcps/health (web dashboard)
Cause: SKIP_PERMISSIONS is not enabled or tool permissions are restricted.Solution: Set in your .env:
SKIP_PERMISSIONS=true
ALLOWED_TOOLS=*
Cause: User not authorized, bot process crashed, or rate limit exceeded.Solution:
  1. Check that your user ID is in ALLOWED_USER_IDS (Telegram) or SLACK_ALLOWED_USER_IDS (Slack)
  2. Check bot logs in channels/{telegram|slack}/ or scripts/logs/
  3. Verify the bot process is running: ps aux | grep bot.py
  4. Restart the bot: ./channels/{channel}/start.sh
Cause: Task took longer than COMMAND_TIMEOUT (default 30 minutes).Solution: Increase the timeout in .env:
COMMAND_TIMEOUT=3600  # 1 hour
If you encounter authentication errors with MCPs (ClickUp, Slack, Google), double-check that your API keys and tokens are valid and have the required permissions.

Need help?

Build docs developers (and LLMs) love