Claude Code Development Environment Setup

Created By
hemant-zangoha year ago
Complete development environment setup for Claude Code with MCP servers, dev containers, and long-running job capabilities
Overview

What is Claude Code Development Environment Setup?

Claude Code Development Environment Setup is a comprehensive setup designed to facilitate the development of Claude Code applications, featuring MCP servers, dev containers, and capabilities for long-running jobs.

How to use Claude Code Development Environment Setup?

To use this setup, clone the repository, set up environment variables, start the development container, initialize MCP servers, and run long-running jobs using provided scripts.

Key features of Claude Code Development Environment Setup?

  • Pre-configured VS Code Dev Container with essential extensions.
  • Docker-based isolated development environment for seamless project management.
  • Integration with various services like Monday.com, Figma, and Playwright for enhanced functionality.
  • Support for long-running jobs with monitoring and logging capabilities.

Use cases of Claude Code Development Environment Setup?

  1. Setting up a development environment for Claude Code applications.
  2. Running automated long-running jobs for code analysis or documentation generation.
  3. Managing projects with integrated tools for task tracking and design system access.

FAQ from Claude Code Development Environment Setup?

  • What are the prerequisites for using this setup?

    You need Docker Desktop, VS Code with Dev Containers extension, Git, and Node.js 20+.

  • Is there a recommended installation method?

    Yes, using the VS Code Dev Container is recommended for ease of use.

  • How can I monitor long-running jobs?

    You can monitor job progress using the provided monitoring scripts.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hemant-zangoh
Star
0
Language
Shell
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago