MCP Server Quick Start
Deploy applications using AI coding assistants like Claude Code, Cursor, or Claude Desktop through the Clue2App MCP Server.
What is MCP?
The Model Context Protocol (MCP) allows AI assistants to interact with external tools and services. Clue2App's MCP server enables you to deploy and manage applications directly through natural language conversations with your AI assistant.
Prerequisites
- Python 3.9 or higher
- Clue2App CLI installed and authenticated
- An AI assistant that supports MCP (Claude Code, Cursor, Claude Desktop)
Installation
Step 1: Install the Clue2App CLI
pip install clue2app-cli
Step 2: Authenticate
c2a login
Step 3: Set Up a Project
# Create a project
c2a projects create --name "MyProject" --namespace "myproject"
# Select it as active
c2a projects select MyProject
Step 4: Install the MCP Server
pip install clue2app-mcp
Configuration
Claude Code
Add to your ~/.claude/claude_code_config.json:
{
"mcpServers": {
"clue2app": {
"command": "clue2app-mcp",
"args": []
}
}
}
Claude Desktop
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"clue2app": {
"command": "python",
"args": ["-m", "clue2app_mcp.server"]
}
}
}
Cursor
Add to your Cursor MCP settings:
{
"mcpServers": {
"clue2app": {
"command": "clue2app-mcp",
"args": []
}
}
}
Quick Deploy Flow
Example Conversations
Deploy an Application
You: Deploy my FastAPI app from https://github.com/user/fastapi-demo
Claude: I'll deploy your FastAPI app to Clue2App.
Uses
c2a_create_apptoolYour app has been deployed! It will be available at
https://fastapi-demo.myproject.apps.clue2.apponce the build completes.
Check Deployment Status
You: What's the status of my-api?
Claude: Let me check the status of your app.
Uses
c2a_get_app_statustoolmy-api Status:
- Build: Ready (completed 5 minutes ago)
- Runtime: Running
- Pods: 2 active
- URL: https://my-api.myproject.apps.clue2.app
View Application Logs
You: Show me the logs for my-api
Claude: Here are the recent logs for my-api:
Uses
c2a_get_app_logstool2024-01-15 10:30:15 INFO Starting application...
2024-01-15 10:30:16 INFO Connected to database
2024-01-15 10:30:17 INFO Server listening on :8080
Trigger a Rebuild
You: Rebuild my-api
Claude: I'll trigger a rebuild for my-api.
Uses
c2a_rebuild_apptoolRebuild triggered successfully! The new build has started.
Set Environment Variables
You: Set DATABASE_URL to postgresql://localhost/mydb for my-api
Claude: I'll set the environment variable for your app.
Uses
c2a_set_env_varstoolEnvironment variable DATABASE_URL has been set. The app will restart with the new configuration.
Available MCP Tools
| Tool | Description |
|---|---|
c2a_auth_status | Check authentication status |
c2a_list_projects | List all your projects |
c2a_get_current_project | Get the current active project |
c2a_use_project | Switch to a different project |
c2a_create_project | Create a new project |
c2a_list_apps | List all apps in current project |
c2a_get_app | Get detailed app information |
c2a_create_app | Deploy a new application |
c2a_get_app_status | Check build and runtime status |
c2a_get_app_logs | View application logs |
c2a_get_build_logs | View build logs |
c2a_rebuild_app | Trigger an app rebuild |
c2a_delete_app | Delete an application |
c2a_set_env_vars | Set environment variables |
c2a_list_git_secrets | List available git secrets |
c2a_get_git_secret | Get git secret details |
Common Workflows
Workflow 1: Full Deployment
You: Create a new project called "production" with namespace "prod"
Claude: [Creates project using c2a_create_project]
You: Deploy https://github.com/myorg/backend-api to the production project
Claude: [Switches project and deploys using c2a_use_project + c2a_create_app]
You: Set the environment variables: NODE_ENV=production, API_KEY=secret123
Claude: [Sets env vars using c2a_set_env_vars]
You: What's the deployment status?
Claude: [Checks status using c2a_get_app_status]
Workflow 2: Debug a Failing App
You: My app backend-api seems to be having issues
Claude: [Checks status using c2a_get_app_status]
The build failed. Let me get the build logs.
[Gets logs using c2a_get_build_logs]
I see the issue - there's a missing dependency in requirements.txt.
You: I've fixed it, rebuild please
Claude: [Triggers rebuild using c2a_rebuild_app]
Workflow 3: Monitor Multiple Apps
You: List all my apps and their status
Claude: [Lists apps using c2a_list_apps]
Here are your apps:
- api-server: Running (2 pods)
- frontend: Running (1 pod)
- worker: Scaled to 0 (no traffic)
Private Repositories
For private repositories, first create a git secret using the CLI:
c2a secrets create git --name my-git-creds --username git --token ghp_xxxx
Then in your AI conversation:
You: Deploy https://github.com/myorg/private-repo using my-git-creds secret
Troubleshooting
MCP Server Not Connecting
-
Verify the MCP server is installed:
which clue2app-mcp -
Check your config file syntax is valid JSON
-
Restart your AI assistant after config changes
Authentication Issues
-
Re-authenticate with the CLI:
c2a login -
Verify authentication:
c2a status
Tools Not Available
-
Ensure you have the latest version:
pip install --upgrade clue2app-mcp -
Check the MCP server logs for errors
Benefits of MCP Integration
Natural Language Deployment
Instead of memorizing CLI commands, just describe what you want:
- "Deploy my app" instead of
c2a deploy app... - "Show me the logs" instead of
c2a logs show... - "What's wrong with my app?" instead of multiple status checks
Context-Aware Assistance
Your AI assistant can:
- Suggest fixes when deployments fail
- Explain build errors in plain English
- Recommend configuration improvements
- Help debug application issues
Seamless Workflow
Deploy directly from your coding session:
- Write code in your editor
- Push to Git
- Ask your AI to deploy
- Get status updates through conversation
Next Steps
- CLI Reference - Full command documentation
- Console Guide - Web console walkthrough
- Deployment Guide - Understanding the deployment process
Need help? Visit our GitHub Issues or contact support.