Codeconductor Ide Orchestrator

Created By
CodeConductor Team6 months ago
CodeConductor IDE Orchestrator gives Claude Desktop full access to your development environment through a secure MCP server. It connects Claude to your VS Code workspace, enabling real file operations, code navigation, Git workflows, and automated development tasks. The server exposes 24 IDE tools, including: File operations — open, read, write, list, search Code intelligence — go to definition, find references, diagnostics Git automation — status, diff, stage, commit, push (Pro) Command execution — run terminal commands safely (Pro) Command Execution Safety: Pro users can run commands through Claude, but everything is protected by a three-tier safety system. Safe commands run automatically, while higher-risk commands require explicit confirmation and are screened for dangerous patterns. This prevents accidental damage and blocks command injection attempts. All operations run locally on your machine, never transmit code, and follow a tier-based permission system (Free vs Pro). Requires the CodeConductor VS Code extension to function. This orchestrator turns Claude into a capable, controlled development assistant that operates directly inside your real project.
Overview

What is CodeConductor IDE Orchestrator?

CodeConductor IDE Orchestrator is a tool that connects Claude Desktop to your development environment, allowing for secure access to your IDE and enabling real file operations, code navigation, Git workflows, and automated development tasks.

How to use CodeConductor IDE Orchestrator?

To use the orchestrator, install the CodeConductor VS Code extension and the MCP bundle in Claude Desktop. Once set up, you can interact with your codebase through Claude by issuing commands and queries.

Key features of CodeConductor IDE Orchestrator?

  • Access to 24 IDE tools for file operations, code intelligence, and Git automation.
  • Command execution with a three-tier safety system to prevent accidental damage.
  • Local operation with no code transmission, ensuring privacy and security.

Use cases of CodeConductor IDE Orchestrator?

  1. Automating Git workflows such as staging, committing, and pushing changes.
  2. Performing code reviews and suggesting improvements based on changes.
  3. Refactoring code safely while ensuring tests pass.
  4. Navigating codebases to find definitions and references.

FAQ from CodeConductor IDE Orchestrator?

  • Is CodeConductor IDE Orchestrator free to use?

The core functionality is available for free, but advanced features require a Pro license.

  • Does it transmit my code to external servers?

No, all operations are performed locally, and no code or project data is transmitted.

  • What happens if I run a risky command?

Risky commands require explicit confirmation and are screened for safety before execution.

Project Info
Created At
6 months ago
Updated At
6 months ago
Author Name
CodeConductor Team
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