Claude Code Development Environment Setup
About
Complete development environment setup for Claude Code with MCP servers, dev containers, and long-running job capabilities
Details
- Author
- hemant-zangoh
- Downloads
- 339
- Categories
- AI
Jump to
- VS Code Dev Container with pre-configured extensions
- Docker-based isolated development environment
- MCP servers: Filesystem, Monday.com, Figma, Playwright
- Long-running jobs with auto-continuation and monitoring
- Automated firewall and permission management
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Claude Code Development Environment SetupCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
What are the prerequisites?
Docker Desktop or Docker Engine with Docker Compose, VS Code with Dev Containers extension (recommended), Git, and Node.js 20+ (included in the container). A GitHub personal access token is required; Monday.com and Figma tokens are optional.
How do I configure API tokens?
Copy .env.example to .env, then edit the file with your tokens: GITHUB_PERSONAL_ACCESS_TOKEN (required), MONDAY_API_TOKEN and FIGMA_TOKEN (optional). Never commit the .env file to the repository.
How do I start MCP servers?
Run ./.devcontainer/init-mcp.sh after starting the container, or manually add each server using claude mcp add commands (e.g., claude mcp add filesystem "npx @modelcontextprotocol/server-filesystem /workspace"). Use claude mcp list to verify.
How do I run a long-running job?
Use ./scripts/run-long-claude-job.sh "task description" or the predefined ./scripts/ten-minute-job.sh. Monitor progress with ./scripts/monitor-job.sh and view logs in /workspace/claude-job-*.log.
What security considerations are there?
Store API tokens in .env and never commit them. Use --dangerously-skip-permissions only in trusted environments. Network firewall rules are automatically configured, and the container runs as a non-root user by default.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"claude code development environment setup": {
"claude-dev-setup": {
"command": "docker",
"args": [
"stats"
]
}
}
}
}
McpServers
{
"claude-dev-setup": {
"command": "docker",
"args": [
"stats"
]
}
}
Claude Code Development Environment Setup
A comprehensive development environment setup for Claude Code with MCP servers, dev containers, and long-running job capabilities.
π Quick Start
1. Clone this repository:
git clone https://github.com/your-username/claude-dev-setup.git
cd claude-dev-setup
2. Set up environment variables:
cp .env.example .env
# Edit .env with your API tokens
3. Start the dev container:
# Using VS Code Dev Containers extension
code .
# Or using Docker Compose directly
docker-compose up -d
4. Initialize MCP servers:
./.devcontainer/init-mcp.sh
5. Start a long-running job:
./scripts/ten-minute-job.sh
π Table of Contents
- Features
- Prerequisites
- Installation
- Configuration
- Usage
- Documentation
- Troubleshooting
- Contributing
β¨ Features
Development Environment
- VS Code Dev Container with pre-configured extensions - Docker-based isolated development environment - Zsh with Oh-My-Zsh for enhanced terminal experience - Git Delta for better diff visualizationMCP (Model Context Protocol) Servers
- Filesystem Server: File operations and project management - Monday.com Integration: Project management and task tracking - Figma Integration: Design system access and component management - Playwright Integration: Browser automation and testingLong-Running Jobs
- Auto-continuation: Jobs that persist across sessions - Monitoring: Real-time progress tracking - Logging: Comprehensive job logging and analysis - Templates: Pre-built job templates for common tasksSecurity & Networking
- Firewall Configuration: Automated network security setup - Permission Management: Controlled access to system resources - Token Management: Secure handling of API credentialsπ§ Prerequisites
- Docker Desktop or Docker Engine with Docker Compose
- VS Code with Dev Containers extension (recommended)
- Git for version control
- Node.js 20+ (included in container)
Required API Tokens
| Service | Required | Purpose | How to Get |
|---------|----------|---------|------------|
| GitHub | β
Yes | Repository operations | GitHub Settings β Developer settings β Personal access tokens |
| Monday.com | βͺ Optional | Project management | Monday.com β Admin β API |
| Figma | βͺ Optional | Design system access | Figma β Settings β Account β Personal access tokens |
π¦ Installation
Method 1: VS Code Dev Container (Recommended)
1. Clone and open in VS Code:
git clone https://github.com/your-username/claude-dev-setup.git
cd claude-dev-setup
code .
2. When prompted, click "Reopen in Container"
- VS Code will automatically build and start the dev container
- All dependencies will be installed automatically
3. Set up environment variables:
cp .env.example .env
# Edit .env with your API tokens
Method 2: Docker Compose
1. Clone the repository:
git clone https://github.com/your-username/claude-dev-setup.git
cd claude-dev-setup
2. Configure environment:
cp .env.example .env
# Edit .env with your API tokens
3. Start the container:
docker-compose up -d
4. Access the container:
docker-compose exec claude-dev zsh
Method 3: Local Installation
If you prefer to run without containers:
1. Install Node.js dependencies:
npm install -g \
@anthropic-ai/claude-code \
@modelcontextprotocol/server-filesystem \
@mondaydotcomorg/monday-api-mcp \
@playwright/mcp \
figma-developer-mcp
2. Set up environment:
cp .env.example .env
source .env
3. Run initialization scripts:
chmod +x .devcontainer/.sh scripts/.sh
./.devcontainer/init-mcp.sh
βοΈ Configuration
Environment Variables
Edit .env file with your configuration:
```bash
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
