Claude Crew 🤖

Created By
d-kimusona year ago
A CLI tool for enhancing Claude Desktop with additional capabilities and workflows
Overview

What is Claude Crew?

Claude Crew is a CLI tool designed to enhance Claude Desktop by creating autonomous coding agents using the Model Context Protocol (MCP). Unlike traditional coding assistants, it focuses on enabling agents to process tasks autonomously.

How to use Claude Crew?

To use Claude Crew, navigate to your project directory and run the setup command: npx claude-crew@latest setup. Follow the interactive prompts to configure your project.

Key features of Claude Crew?

  • Easy setup through an interactive dialog
  • Smooth integration with Claude Desktop
  • Automatic instruction generation for Claude Projects
  • Customizable project workflow commands
  • Multi-language support with TypeScript
  • Enhanced context understanding through OpenAI embedding (optional)
  • Memory Bank functionality for persistent project knowledge

Use cases of Claude Crew?

  1. Creating autonomous coding agents for software development
  2. Automating project workflows and task execution
  3. Enhancing coding efficiency through context-aware tools

FAQ from Claude Crew?

  • What are the requirements for using Claude Crew?

    You need Claude Desktop, an OpenAI API key (optional), Docker, and Node.js >= v20.

  • Can Claude Crew be used with multiple projects?

    Yes! Each project generates its own unique configuration to prevent conflicts.

  • Is there support for other programming languages?

    Yes, while full support is provided for TypeScript, basic file operations are available for other languages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
d-kimuson
Star
24
Language
TypeScript
License
MIT license
Tags

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)

2 days ago