-
Notifications
You must be signed in to change notification settings - Fork 0
Description
🎯 Overview
Enable per-project MCP adapter configuration and discovery with automatic Cursor integration, centralized storage, and a unified CLI experience.
Key Insight: Users install @lytics/dev-agent globally once, then configure adapters per-project. Each project's .dev-agent/config.json defines which adapters to load, and dev-agent mcp init automatically adds the project to Cursor's MCP config.
🏗️ Architecture
Core Components
- Centralized Storage - All repository indexes stored globally in
~/.dev-agent/indexes/(enables cross-repo search, clean project dirs) - Project Configuration - Per-project
.dev-agent/config.jsondefines adapters and settings - Adapter Discovery - Automatic discovery and loading of built-in, npm, and local adapters
- CLI Management - Unified commands for MCP setup and adapter management
User Flow
# One-time global install
npm install -g @lytics/dev-agent
# Per-project setup
cd my-project
dev-agent init # Create config + index repository
dev-agent mcp init # Add to Cursor MCP config
dev-agent adapter install @company/mcp-adapter-jira # Install custom adapter📋 Sub-Issues
This epic is broken down into three focused sub-issues:
- Foundation: Storage + Config System #52: Foundation - Storage + Config System - Centralized storage, config schema, lazy loading
- Adapters: Discovery + Loading System #53: Adapters - Discovery + Loading System - Adapter discovery algorithm, loading mechanism
- UX: CLI Management Commands #54: UX - CLI Management Commands - User-facing commands for MCP + adapter management
✅ Success Criteria
- Users can run
dev-agent init && dev-agent mcp initto fully configure a project - Custom adapters can be installed via
dev-agent adapter install - Team members can clone and get same adapter setup
- Different projects can have different adapters from same global install
- No manual editing of
~/.cursor/mcp.jsonrequired - Indexes stored centrally, enabling cross-repository search
- Built-in adapters can be disabled per-project
🔗 Related Issues
- Depends on: Explore + GitHub Adapters #30 (Explore + GitHub Adapters) - establishes adapter patterns
- Blocks: Documentation + Examples #32 (Documentation) - need to document new setup flow
- Blocks: Integration Testing + Release #33 (Integration Testing) - need to test adapter discovery
- Related: feat(mcp): add structured metadata field to MCP tool responses #51 (Metadata field) - will enhance adapter responses
Estimate: 3-4 days (across 3 sub-issues)
Priority: High (blocks documentation and release)
Milestone: v1.0 - MCP Integration Complete
Sub-issues
Metadata
Metadata
Assignees
Labels
No labels