Enhanced Development Environment with MCP Servers

Created By
danmaraudaa year ago
Enhanced development environment with MCP servers, UV package manager, and Open Interpreter
Overview

What is Enhanced Development Environment?

The Enhanced Development Environment is a comprehensive setup designed for developers, featuring the UV package manager, Open Interpreter, and Model Context Protocol servers to streamline the Python development process.

How to use Enhanced Development Environment?

To use this environment, developers can deploy it via Docker or Vagrant. The system provides a structured directory with configuration files and tools for various development tasks.

Key features of Enhanced Development Environment?

  • Fast Python package management with the UV package manager
  • An array of modern CLI tools including exa, bat, and ripgrep
  • Development tools such as Git, Vim, and Tmux
  • Customizable configurations for individual developer needs
  • Docker and Vagrant support for easy container and VM management

Use cases of Enhanced Development Environment?

  1. Managing Python projects with ease using UV and virtual environments
  2. Utilizing modern CLI tools to enhance productivity
  3. Collaborating in teams through the standardized development environment

FAQ from Enhanced Development Environment?

  • How do I install packages with the UV package manager?

Use the command 'python-install [package_name]' to add new packages.

  • Can I customize my environment settings?

Yes! You can edit ' ~/.zshrc.local' and ' ~/.config/uv/uvconfig.toml' for local configurations.

  • What if I run into issues while using the environment?

Check the troubleshooting section that provides commands like 'uv-clean' and 'uv-doctor' for problem resolution.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
danmarauda
Star
-
Language
-
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