repositoryworkspaceclaude-codedeveloper-tools
Scans local repositories through MCP and exposes AgenticWorkspace workspace-generation workflows to AI agents.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Overview
Use cases
Scan a repository to identify its language, package manager, and monorepo structure
Create a `.workspace/` directory with root context and handoff support
Install Claude Code session hooks for a repository
Check existing agent configuration without overwriting it
Key features
Repository stack detection
Structured JSON results
Workspace and session-handoff scaffolding
Claude Code adapter installation
Non-destructive configuration detection
Partial-state recovery
Capabilities & Tool Schemas
Inspect callable tools, capabilities, and parameters exposed to AI agents by Agenticworkspace.
Extracted Tool Capabilities
Repository stack detection
Structured JSON results
Workspace and session-handoff scaffolding
Claude Code adapter installation
Non-destructive configuration detection
Partial-state recovery
How Agenticworkspace works
What agenticworkspace MCP server does
The agenticworkspace MCP server connects an AI agent to a local repository and the AgenticWorkspace scan/scaffold pipeline. Its purpose is to turn repository metadata into a structured .workspace/ directory that agents can use for progressive context and session handoffs.
The underlying project is available as both JavaScript/TypeScript and Python packages. The JavaScript package requires Node.js 20 or newer, while the Python package provides an equivalent CLI and library pipeline. Both implementations use the same .workspace/ directory shape.
A repository scan can identify JavaScript or TypeScript, Python, and lighter-weight signals for Rust, Go, and Ruby. It also reports package-manager information for npm, pnpm, and Yarn, along with whether the repository is a monorepo and how many packages it contains.
How it works
The agenticworkspace MCP server delegates repository workspace operations to the AgenticWorkspace CLI rather than implementing a separate repository model. The CLI accepts a target path, scans manifest and configuration files, and writes generated workspace data under the repository's .workspace/ directory.
The generated structure can include a workspace metadata file, root context markdown, a handoff directory, and adapter files. The documented initialization flow also installs Claude Code hooks for session start, pre-tool calls, and session-end handoff generation. These hooks are configured through files under .workspace/adapters/claude-code/.
Existing agent-related configuration is detected without being overwritten. The scan checks for CLAUDE.md, AGENTS.md, Cursor rules, and GitHub Copilot instructions. It also detects Serena, GitNexus-style configuration, and repo-harness state without reading from or modifying those systems.
Tools and capabilities
The project documents CLI operations for initialization, scanning, status checks, adapter installation, and creating handoffs. Each subcommand supports structured JSON output, including error cases, so an MCP caller can consume results without parsing terminal-oriented text.
Key capabilities include:
- Detecting repository language, package manager, and monorepo package count.
- Creating
.workspace/context and handoff files. - Installing the documented Claude Code adapter and its hook scripts.
- Reporting existing configuration and detected memory backends.
- Identifying interrupted or malformed initialization state instead of silently replacing it.
- Supporting extension through separate memory-backend and adapter interfaces.
Generated shell values pass through allowlist and quoting checks before being embedded in hooks. The project also supports partial-state recovery through an interactive repair, reset, or abort flow, with structured errors in JSON mode.
Setup and configuration
The repository provides two installation paths. JavaScript/TypeScript users can run npx agenticworkspace-cli init, install the package globally, or build it from source with npm. Python users can install agenticworkspace-cli from PyPI and run agenticworkspace init --path /path/to/repository. The source-based Python workflow installs from the repository's python directory.
The documented initialization command accepts a repository path and can emit JSON results with --json. A successful run reports the target, detected stack, existing configuration, memory-backend findings, context budget, adapter status, and workspace location.
No MCP-specific environment variables, client configuration, transport, or server launch command is specified in the provided material. Configure those details only from additional project documentation or the package's actual MCP entry point.
Limitations and notes
This is identified as a version 0.1 release, so its documented scope is limited to the implemented scan, scaffold, and adapter pipeline. The README does not establish support for adapters beyond the working Claude Code adapter, nor does it name specific MCP clients.
The agenticworkspace version reported in JSON is an internal schema marker and may differ from the installed npm or PyPI package version. The generated workspace is repository-local, and the tool is designed to avoid modifying detected external memory or agent-configuration systems.
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
npm downloads
221
Package downloads in the last 30 days.
Last commit
16d ago
Most recent push to the default branch.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Agenticworkspace
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/agenticworkspace)HTML Embed
<a href="https://allmcps.com/mcp/agenticworkspace"><img src="https://allmcps.com/api/badge/agenticworkspace?style=directory" alt="Agenticworkspace on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
43Quality signal: Fair · 43/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools16/30
Adoption & activity6/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 6d ago via OSV.dev · agenticworkspace-cli (npm)
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.