Claude Code Development Environment Setup

@hemant-zangoh

About Claude Code Development Environment Setup

Complete development environment setup for Claude Code with MCP servers, dev containers, and long-running job capabilities

#claude-dev-setup #development-environment #mcp-servers

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "claude-dev-setup": {
      "command": "docker",
      "args": [
        "stats"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Claude Code Development Environment Setup?

A comprehensive development environment setup for Claude Code that integrates multiple MCP servers, VS Code Dev Containers, and long-running job capabilities. It provides an isolated, Docker-based environment with pre-configured MCP servers for filesystem operations, Monday.com project management, Figma design system access, and Playwright browser automation. Designed for developers who need a consistent, reproducible workspace for Claude Code projects.

How to use Claude Code Development Environment Setup?

Clone the repository, copy .env.example to .env, populate API tokens (GitHub required; Monday.com and Figma optional), then start the dev container via VS Code's "Reopen in Container" or with docker-compose up -d. Run ./.devcontainer/init-mcp.sh to initialize MCP servers, and use scripts like ./scripts/ten-minute-job.sh or ./scripts/run-long-claude-job.sh "task" for long-running jobs. MCP servers can also be added manually with claude mcp add commands.

Key features of Claude Code Development Environment Setup

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

Use cases of Claude Code Development Environment Setup

Setting up a consistent, reproducible Claude Code workspace across machines
Integrating project management tasks via Monday.com MCP server
Automating browser testing and web scraping with Playwright MCP
Running hours-long code analysis or documentation generation jobs that persist across sessions
Accessing design system components with the Figma MCP server

FAQ from Claude Code Development Environment Setup

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.

Frequently asked questions

What are the prerequisites?

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.

Comments

Basic information

More AI & Agents MCP servers

21st.dev Magic AI Agent

21st-dev

It's like v0 but in your Cursor/WindSurf/Cline. 21st dev Magic MCP server for working with your frontend like Magic

5.3K

Lumify Sports Intelligence

Lumify

Agent-ready sports intelligence API: live scores, odds, line movement, public betting splits, and explainable bet confidence — via 16 MCP tools at https://lumify.ai/mcp. Get a free key instantly — no signup, email, or ca

Unreal Engine Generative AI Support Plugin

prajwalshettydev

Unreal Engine plugin for LLM/GenAI models & MCP UE5 server. OpenAI GPT-5, Deepseek R1, Claude Opus/Sonnet, Gemini 3, Grok 4, Alibaba Qwen, Kimi, ElevenLabs TTS, Inworld, OpenRouter, Groq, GLM, Ollama, Local, Meshy, Tripo, Hunyuan3D, Rodin, fal, Dashscope, Seedream. NPC AI, agenti

622

bsv.cx

Andy Rowe

Timestamp and verify evidence on-chain. Let your agent prove what it saw and when. bsv.cx gives an AI agent verifiable memory. Timestamp a hash of any output, archive a web page as it looked, or fetch a URL with a recei

Solon Ai

opensolon

Java AI application development framework (supports LLM-tool,skill; RAG; MCP; Agent-ReAct,Team-Agent). Compatible with java8 ~ java25. It can also be embedded in SpringBoot, jFinal, Vert.x, Quarkus, and other frameworks.

416