mcp-consultant-tools 3.0.0 → 3.1.0

package/README.md

@@ -1,983 +1,332 @@
 # MCP Consultant Tools
 
-A Model Context Protocol (MCP) server that provides intelligent access to PowerPlatform/Dataverse entities, Azure DevOps, and Figma designs. This tool offers context-aware assistance, entity exploration, and metadata access across multiple platforms.
+A Model Context Protocol (MCP) server providing intelligent access to PowerPlatform/Dataverse, Azure DevOps, and Figma through an AI-friendly interface.
 
-Key features:
-- **PowerPlatform/Dataverse**: Rich entity metadata exploration with formatted, context-aware prompts, advanced OData query support, comprehensive relationship mapping
-- **Azure DevOps**: Wiki search, work item management, WIQL queries, and team collaboration tools
-- **Figma**: Design data extraction with simplified AI-friendly format, component analysis, and style deduplication
-- AI-assisted query building and data modeling through AI agent
-- Full access to entity attributes, relationships, and global option sets
+## Overview
 
-## Installation
+This MCP server enables AI assistants to:
+- **PowerPlatform/Dataverse**: Explore entity metadata, query records, inspect plugins, analyze workflows and flows
+- **Azure DevOps**: Search wikis, manage work items, execute WIQL queries
+- **Figma**: Extract design data in simplified, AI-friendly format
 
-You can install and run this tool in two ways:
+All integrations are **optional** - configure only the services you need.
 
-### Option 1: Install globally
+## Quick Start
 
-```bash
-npm install -g mcp-consultant-tools
-```
+### Installation
 
-Then run it:
+Run directly with npx (no installation needed):
 
 ```bash
-mcp-consultant-tools
+npx mcp-consultant-tools@latest
 ```
 
-### Option 2: Run directly with npx
-
-Run without installing:
+Or install globally:
 
 ```bash
-npx mcp-consultant-tools
+npm install -g mcp-consultant-tools
 ```
 
-## Configuration
-
-This is an MCP server designed to work with MCP-compatible clients like Claude Desktop, Cursor, or Claude Code (VS Code extension).
+### Configuration
 
-### Quick Start: VS Code (Claude Code) Configuration
+#### Claude Desktop
 
-For VS Code with Claude Code extension, create a `.vscode/mcp.json` file in your repository:
+Add to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):
 
 ```json
 {
-  "servers": {
+  "mcpServers": {
     "mcp-consultant-tools": {
       "command": "npx",
-      "args": ["-y", "mcp-consultant-tools"],
+      "args": ["-y", "mcp-consultant-tools@latest"],
       "env": {
         "POWERPLATFORM_URL": "https://yourenvironment.crm.dynamics.com",
-        "POWERPLATFORM_CLIENT_ID": "your-azure-app-client-id",
-        "POWERPLATFORM_CLIENT_SECRET": "your-azure-app-client-secret",
-        "POWERPLATFORM_TENANT_ID": "your-azure-tenant-id",
-        "AZUREDEVOPS_ORGANIZATION": "your-organization-name",
-        "AZUREDEVOPS_PAT": "your-personal-access-token",
+        "POWERPLATFORM_CLIENT_ID": "your-client-id",
+        "POWERPLATFORM_CLIENT_SECRET": "your-client-secret",
+        "POWERPLATFORM_TENANT_ID": "your-tenant-id",
+
+        "AZUREDEVOPS_ORGANIZATION": "your-org",
+        "AZUREDEVOPS_PAT": "your-pat",
         "AZUREDEVOPS_PROJECTS": "Project1,Project2",
-        "AZUREDEVOPS_API_VERSION": "7.1",
-        "AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE": "true",
-        "AZUREDEVOPS_ENABLE_WORK_ITEM_DELETE": "false",
-        "AZUREDEVOPS_ENABLE_WIKI_WRITE": "false",
-        "FIGMA_API_KEY": "your-figma-personal-access-token",
-        "FIGMA_OAUTH_TOKEN": "",
-        "FIGMA_USE_OAUTH": "false"
+
+        "FIGMA_API_KEY": "your-figma-token"
       }
     }
   }
 }
 ```
 
-**After configuration:**
-1. Save the `.vscode/mcp.json` file
-2. Reload VS Code window
-3. The MCP server will be available in Claude Code
+Restart Claude Desktop after saving.
 
-**Note:** You can omit PowerPlatform, Azure DevOps, or Figma credentials if you only need certain integrations (see Environment Variables Reference below).
+#### VS Code (Claude Code)
 
-### Quick Start: Claude Desktop Configuration
-
-Add this to your Claude Desktop config file at `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):
+Create `.vscode/mcp.json` in your project:
 
 ```json
 {
-  "mcpServers": {
+  "servers": {
     "mcp-consultant-tools": {
       "command": "npx",
-      "args": ["-y", "mcp-consultant-tools"],
+      "args": ["-y", "mcp-consultant-tools@latest"],
       "env": {
         "POWERPLATFORM_URL": "https://yourenvironment.crm.dynamics.com",
-        "POWERPLATFORM_CLIENT_ID": "your-azure-app-client-id",
-        "POWERPLATFORM_CLIENT_SECRET": "your-azure-app-client-secret",
-        "POWERPLATFORM_TENANT_ID": "your-azure-tenant-id",
-        "AZUREDEVOPS_ORGANIZATION": "your-organization-name",
-        "AZUREDEVOPS_PAT": "your-personal-access-token",
-        "AZUREDEVOPS_PROJECTS": "Project1,Project2",
-        "AZUREDEVOPS_API_VERSION": "7.1",
-        "AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE": "true",
-        "AZUREDEVOPS_ENABLE_WORK_ITEM_DELETE": "false",
-        "AZUREDEVOPS_ENABLE_WIKI_WRITE": "false",
-        "FIGMA_API_KEY": "your-figma-personal-access-token",
-        "FIGMA_OAUTH_TOKEN": "",
-        "FIGMA_USE_OAUTH": "false"
+        "POWERPLATFORM_CLIENT_ID": "your-client-id",
+        "POWERPLATFORM_CLIENT_SECRET": "your-client-secret",
+        "POWERPLATFORM_TENANT_ID": "your-tenant-id"
       }
     }
   }
 }
 ```
 
-### Local Development Configuration
-
-For local development and testing, you can run the server directly from your cloned repository using Node.js. Add this to your Claude Desktop config:
-
-```json
-{
-  "mcpServers": {
-    "mcp-consultant-tools-dev": {
-      "command": "node",
-      "args": ["/absolute/path/to/mcp-consultant-tools/build/index.js"],
-      "env": {
-        "POWERPLATFORM_URL": "https://yourenvironment.crm.dynamics.com",
-        "POWERPLATFORM_CLIENT_ID": "your-azure-app-client-id",
-        "POWERPLATFORM_CLIENT_SECRET": "your-azure-app-client-secret",
-        "POWERPLATFORM_TENANT_ID": "your-azure-tenant-id",
-        "AZUREDEVOPS_ORGANIZATION": "your-organization-name",
-        "AZUREDEVOPS_PAT": "your-personal-access-token",
-        "AZUREDEVOPS_PROJECTS": "Project1,Project2",
-        "AZUREDEVOPS_API_VERSION": "7.1",
-        "AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE": "true",
-        "AZUREDEVOPS_ENABLE_WORK_ITEM_DELETE": "false",
-        "AZUREDEVOPS_ENABLE_WIKI_WRITE": "false",
-        "FIGMA_API_KEY": "your-figma-personal-access-token",
-        "FIGMA_OAUTH_TOKEN": "",
-        "FIGMA_USE_OAUTH": "false"
-      }
-    }
-  }
-}
-```
-
-**Important:** Replace `/absolute/path/to/mcp-consultant-tools` with the actual path to your cloned repository (e.g., `/Users/yourname/Repo/mcp-consultant-tools`).
-
-### Environment Variables Reference
-
-**Note:** All integrations (PowerPlatform, Azure DevOps, Figma) are optional. You can configure only the services you need:
-- PowerPlatform only: Set `POWERPLATFORM_*` variables
-- Azure DevOps only: Set `AZUREDEVOPS_*` variables
-- Figma only: Set `FIGMA_*` variables
-- Any combination: Set only the variables you need
-
-**PowerPlatform/Dataverse (Optional):**
-- `POWERPLATFORM_URL`: Your PowerPlatform environment URL
-- `POWERPLATFORM_CLIENT_ID`: Azure AD app registration client ID
-- `POWERPLATFORM_CLIENT_SECRET`: Azure AD app registration client secret
-- `POWERPLATFORM_TENANT_ID`: Azure tenant ID
-
-**Azure DevOps (Optional):**
-- `AZUREDEVOPS_ORGANIZATION`: Your Azure DevOps organization name
-- `AZUREDEVOPS_PAT`: Personal Access Token with appropriate scopes
-- `AZUREDEVOPS_PROJECTS`: Comma-separated list of allowed projects
-- `AZUREDEVOPS_API_VERSION`: API version (default: "7.1")
-- `AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE`: Enable work item write operations (default: "false")
-- `AZUREDEVOPS_ENABLE_WORK_ITEM_DELETE`: Enable work item delete operations (default: "false")
-- `AZUREDEVOPS_ENABLE_WIKI_WRITE`: Enable wiki write operations (default: "false")
-
-**Figma (Optional):**
-- `FIGMA_API_KEY`: Figma Personal Access Token (generate at: https://www.figma.com/developers/api#authentication)
-- `FIGMA_OAUTH_TOKEN`: Alternative to API key for OAuth authentication
-- `FIGMA_USE_OAUTH`: Set to "true" if using OAuth token instead of API key (default: "false")
-
-**How to get a Figma API Key:**
-1. Go to https://www.figma.com/developers/api#authentication
-2. Scroll to "Personal Access Tokens"
-3. Click "Get personal access token"
-4. Log in to Figma
-5. Generate new token and copy it to your config
-
-**After configuration:**
-1. Save the config file
-2. Completely restart Claude Desktop (quit and reopen)
-3. The MCP server will be available in Claude Desktop
-
-## Usage
-
-Once configured, the MCP server will expose tools for retrieving PowerPlatform entity metadata and records.
-
-### Available Tools
-
-The server provides **30 tools** across PowerPlatform, Azure DevOps, and Figma integrations.
-
-### PowerPlatform/Dataverse Tools
-
-#### Entity Metadata & Data Tools
-- `get-entity-metadata`: Get metadata about a PowerPlatform entity
-- `get-entity-attributes`: Get attributes/fields of a PowerPlatform entity
-- `get-entity-attribute`: Get a specific attribute/field of a PowerPlatform entity
-- `get-entity-relationships`: Get relationships for a PowerPlatform entity
-- `get-global-option-set`: Get a global option set definition
-- `get-record`: Get a specific record by entity name and ID
-- `query-records`: Query records using an OData filter expression
-
-#### Plugin Registration & Validation Tools
-- `get-plugin-assemblies`: List all plugin assemblies in the environment
-- `get-plugin-assembly-complete`: Get comprehensive plugin assembly information including all types, steps, images, and automatic validation
-- `get-entity-plugin-pipeline`: Get all plugins that execute on a specific entity, organized by message and execution order
-- `get-plugin-trace-logs`: Query plugin trace logs with filtering and exception parsing
-
-#### Workflow & Power Automate Flow Tools
-- `get-flows`: List all Power Automate cloud flows (category = 5)
-- `get-flow-definition`: Get complete flow definition including JSON logic from clientdata field
-- `get-flow-runs`: Get flow run history with status, duration, and error details
-- `get-workflows`: List all classic Dynamics workflows (category = 0)
-- `get-workflow-definition`: Get complete workflow definition including XAML and trigger configuration
-
-### Azure DevOps Tools
-
-#### Wiki Tools
-- `get-wikis`: List all wikis in a project
-- `search-wiki-pages`: Full-text search across wiki pages with highlighting
-- `get-wiki-page`: Get specific wiki page content and metadata
-- `create-wiki-page`: Create new wiki page (requires `AZUREDEVOPS_ENABLE_WIKI_WRITE=true`)
-- `update-wiki-page`: Update existing wiki page (requires `AZUREDEVOPS_ENABLE_WIKI_WRITE=true`)
-
-#### Work Item Tools
-- `get-work-item`: Get work item by ID with full details
-- `query-work-items`: Execute WIQL queries to find work items
-- `get-work-item-comments`: Get discussion comments for a work item
-- `add-work-item-comment`: Add comment to work item (requires `AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE=true`)
-- `update-work-item`: Update work item fields using JSON Patch (requires `AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE=true`)
-- `create-work-item`: Create new work item (requires `AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE=true`)
-- `delete-work-item`: Delete work item (requires `AZUREDEVOPS_ENABLE_WORK_ITEM_DELETE=true`)
-
-### Figma Tools
-- `get-figma-data`: Get comprehensive Figma design data including layout, text, styles, and components. Fetches from Figma API and transforms into simplified, AI-friendly format. Can fetch entire files or specific nodes.
-- `download-figma-images`: Placeholder for future image download functionality (Coming in v2)
-
-## MCP Prompts
-
-The server includes **12 prompts** that provide formatted, context-rich information across all integrations.
-
-### Available Prompts
-
-#### Entity Prompts
-1. **entity-overview**: Comprehensive overview of a PowerPlatform entity
-2. **attribute-details**: Detailed information about a specific entity attribute
-3. **query-template**: OData query template for an entity with example filters
-4. **relationship-map**: Visual map of entity relationships
-
-#### PowerPlatform Plugin Prompts
-5. **plugin-deployment-report**: Generate a comprehensive deployment report for a plugin assembly with validation warnings
-6. **entity-plugin-pipeline-report**: Generate a visual execution pipeline showing all plugins for an entity in order
-
-#### PowerPlatform Workflow & Flow Prompts
-7. **flows-report**: Comprehensive report of all Power Automate flows grouped by state
-8. **workflows-report**: Comprehensive report of all classic Dynamics workflows grouped by state
-
-#### Azure DevOps Prompts
-9. **wiki-search-results**: Search Azure DevOps wiki pages with formatted results and content snippets
-10. **wiki-page-content**: Get a formatted wiki page with navigation context and sub-pages
-11. **work-item-summary**: Get a comprehensive summary of a work item with details and comments
-12. **work-items-query-report**: Execute a WIQL query and get results grouped by state/type
-
-## Prompt Examples
-
-Here are some examples of how you can interact with assistant using the PowerPlatform MCP prompts:
-
-### 1. Entity Understanding
-
-You can ask assistant about entities in natural language:
-
-```
-User: "Tell me about the Account entity in our PowerPlatform environment"
-
-Response:
-[uses ENTITY_OVERVIEW prompt internally]
-
-Here's what I found about the Account entity:
-- It's a core business entity representing customers and potential customers
-- The primary identifier is 'accountid' and the primary name field is 'name'
-- Key fields include:
-  * name (Account Name)
-  * emailaddress1 (Email)
-  * telephone1 (Main Phone)
-  * revenue (Annual Revenue)
-- It has 42 one-to-many relationships and 8 many-to-many relationships
-```
-
-### 2. Building Queries
-
-You can ask for help constructing queries:
-
-```
-User: "Help me write a query to find active accounts with revenue over $1M in California"
-
-Response:
-[uses QUERY_TEMPLATE prompt internally]
-
-Here's the OData query you need:
-accounts?$select=name,revenue,statecode,address1_stateorprovince
-&$filter=statecode eq 0 
-    and revenue gt 1000000 
-    and address1_stateorprovince eq 'California'
-&$orderby=revenue desc
-
-This query:
-1. Selects relevant fields
-2. Filters for active accounts (statecode eq 0)
-3. Checks revenue > $1M
-4. Filters for California location
-5. Orders by revenue highest to lowest
-```
-
-### 3. Understanding Relationships
-
-You can explore entity relationships naturally:
-
-```
-User: "How are Accounts and Contacts related in our system?"
-
-Response:
-[uses RELATIONSHIP_MAP prompt for both entities internally]
-
-Here are the key relationships between Accounts and Contacts:
+Reload VS Code window after saving.
 
-1. Primary Contact (One-to-Many):
-   - account_primary_contact: Account (1) → Contact (N)
-   - An account can have many contacts, but one designated as primary
+**Note:** Omit credentials for integrations you don't need. See [SETUP.md](SETUP.md) for complete configuration options.
 
-2. Customer Relationship:
-   - contact_customer_accounts: Contact (N) ← Account (1)
-   - Contacts can be associated with customer accounts
+## Available Tools
 
-3. Additional Relationships:
-   - accountleads_association: For lead tracking
-   - account_connections: For relationship management
-```
+### PowerPlatform/Dataverse (15 tools)
 
-### 4. Field/Attribute Investigation
+**Entity & Data:**
+- `get-entity-metadata` - Get entity metadata
+- `get-entity-attributes` - Get entity fields/attributes
+- `get-entity-attribute` - Get specific attribute details
+- `get-entity-relationships` - Get entity relationships
+- `get-global-option-set` - Get option set definitions
+- `get-record` - Get a specific record
+- `query-records` - Query records with OData filters
 
-You can ask about specific fields:
+**Plugins:**
+- `get-plugin-assemblies` - List plugin assemblies
+- `get-plugin-assembly-complete` - Full assembly details with validation
+- `get-entity-plugin-pipeline` - Plugin execution order for entity
+- `get-plugin-trace-logs` - Query plugin execution logs
 
-```
-User: "What kind of field is the revenue field on Account?"
-
-Response:
-[uses ATTRIBUTE_DETAILS prompt internally]
-
-The revenue field on Account is:
-- Data Type: Money
-- Format: Currency
-- Not required
-- Searchable: Yes
-- Used for: Tracking annual revenue for the account
-- Can be used in advanced find and filtered views
-```
+**Workflows & Flows:**
+- `get-flows` - List Power Automate flows
+- `get-flow-definition` - Get flow definition and logic
+- `get-flow-runs` - Get flow run history
+- `get-workflows` - List classic workflows
+- `get-workflow-definition` - Get workflow definition
 
-### 5. Complex Data Modeling
+### Azure DevOps (12 tools)
 
-You can get help with data modeling decisions:
+**Wikis:**
+- `get-wikis` - List wikis in project
+- `search-wiki-pages` - Full-text search across wikis
+- `get-wiki-page` - Get wiki page content
+- `create-wiki-page` - Create new wiki page (requires write permission)
+- `update-wiki-page` - Update wiki page (requires write permission)
 
-```
-User: "I need to design a solution for tracking product reviews. Which entities should I relate to?"
+**Work Items:**
+- `get-work-item` - Get work item by ID
+- `query-work-items` - Execute WIQL queries
+- `get-work-item-comments` - Get work item comments
+- `add-work-item-comment` - Add comment (requires write permission)
+- `update-work-item` - Update work item fields (requires write permission)
+- `create-work-item` - Create new work item (requires write permission)
+- `delete-work-item` - Delete work item (requires delete permission)
 
-Response:
-[uses multiple ENTITY_OVERVIEW and RELATIONSHIP_MAP prompts internally]
+### Figma (2 tools)
 
-Based on the existing data model, here's a suggested approach:
+- `get-figma-data` - Get design data (layout, text, styles, components)
+- `download-figma-images` - Download images (coming in v2)
 
-1. Product (existing entity):
-   - Already has relationships with:
-     * Price lists
-     * Product categories
-     * Inventory units
+## Available Prompts
 
-2. New Review entity should relate to:
-   - Product (N:1) - Each review is for one product
-   - Contact (N:1) - Reviews are written by contacts
-   - Account (N:1) - Optional link to company if B2B review
+The server includes **12 prompts** that provide formatted, context-rich output:
 
-Here's a sample lookup field structure...
-[continues with detailed implementation guidance]
-```
+**PowerPlatform:**
+- `entity-overview` - Comprehensive entity overview
+- `attribute-details` - Detailed attribute information
+- `query-template` - OData query examples
+- `relationship-map` - Visual relationship mapping
+- `plugin-deployment-report` - Plugin validation for PR reviews
+- `entity-plugin-pipeline-report` - Visual plugin execution pipeline
+- `flows-report` - Power Automate flows report
+- `workflows-report` - Classic workflows report
 
-### 6. Debugging Assistance
+**Azure DevOps:**
+- `wiki-search-results` - Formatted wiki search results
+- `wiki-page-content` - Formatted wiki page with navigation
+- `work-item-summary` - Comprehensive work item summary
+- `work-items-query-report` - Formatted WIQL query results
 
-You can get help troubleshooting:
+## Documentation
 
-```
-User: "Why am I getting 'invalid property' when querying account.customertypecode?"
-
-Response:
-[uses ATTRIBUTE_DETAILS prompt internally]
-
-I see the issue. The field 'customertypecode' is actually named 'customertype' in your environment. Here's the correct field information:
-- Logical Name: customertype
-- Type: OptionSetValue
-- Valid Values:
-  * 1 = Competitor
-  * 2 = Consultant
-  * 3 = Customer
-  * 4 = Investor
-  * 5 = Partner
-  * 6 = Influencer
-
-Try updating your query to use 'customertype' instead of 'customertypecode'.
-```
+- **[SETUP.md](SETUP.md)** - Complete setup guide with credentials, troubleshooting, and security
+- **[TOOLS.md](TOOLS.md)** - Full reference for all 30 tools and 12 prompts
+- **[USAGE.md](USAGE.md)** - Examples and use cases for all integrations
+- **[CLAUDE.md](CLAUDE.md)** - Architecture details and development guide
 
-These examples show how AI assistant can leverage the MCP prompts to provide context-aware, accurate assistance for PowerPlatform development tasks. The AI understands your environment's specific configuration and can help with both simple queries and complex architectural decisions.
+## Key Features
 
-## Plugin Registration & Validation
+### PowerPlatform Plugin Validation
 
-The server includes powerful tools for plugin discovery, validation, and troubleshooting. These tools eliminate the need for the Plugin Registration Tool for most inspection tasks and enable AI-assisted PR reviews.
-
-### Use Cases
-
-#### 1. Discover Plugin Assemblies
-```javascript
-// List all custom (unmanaged) plugin assemblies
-await mcpClient.invoke("get-plugin-assemblies", {
-  includeManaged: false
-});
-```
-
-**Output:**
-```json
-{
-  "totalCount": 10,
-  "assemblies": [
-    {
-      "name": "MyCompany.Plugins",
-      "version": "1.0.0.5",
-      "isolationMode": "Sandbox",
-      "modifiedOn": "2024-01-15T10:30:00Z",
-      "modifiedBy": "John Doe"
-    }
-  ]
-}
-```
-
-#### 2. Validate Plugin Deployment (PR Review)
-```javascript
-// Get comprehensive assembly info with automatic validation
-await mcpClient.invoke("get-plugin-assembly-complete", {
-  assemblyName": "MyCompany.Plugins",
-  includeDisabled: false
-});
-```
-
-**Returns:**
-- Assembly metadata (version, isolation mode, last modified)
-- All plugin types (class names)
-- All registered steps with:
-  - Stage (PreValidation/PreOperation/PostOperation)
-  - Mode (Synchronous/Asynchronous)
-  - Execution rank
-  - Filtering attributes
-  - Pre/Post images with column lists
-- **Automatic validation** detecting:
-  - Missing filtering attributes (performance issue)
-  - Missing images (potential runtime errors)
-  - Disabled steps
-  - Configuration issues
-
-#### 3. View Entity Plugin Pipeline
-```javascript
-// See all plugins that run on an entity in execution order
-await mcpClient.invoke("get-entity-plugin-pipeline", {
-  entityName": "account",
-  messageFilter": "Update"  // Optional: filter by message
-});
-```
-
-**Shows:**
-- All plugins organized by stage and rank
-- Execution order
-- Filtering attributes per step
-- Images configured
-- Assembly versions
-
-#### 4. Troubleshoot with Trace Logs
-```javascript
-// Query recent plugin failures
-await mcpClient.invoke("get-plugin-trace-logs", {
-  entityName: "account",
-  exceptionOnly: true,
-  hoursBack: 24,
-  maxRecords: 50
-});
-```
-
-**Returns:**
-- Parsed exception details
-- Exception type and message
-- Stack traces
-- Execution duration
-- Correlation IDs for further investigation
-
-### Plugin Validation for PR Reviews
-
-When reviewing plugin PRs, use the `plugin-deployment-report` prompt for a human-readable validation report:
+Automatically validate plugin deployments for PR reviews:
 
 ```javascript
+// Get complete validation report
 await mcpClient.callPrompt("plugin-deployment-report", {
   assemblyName: "MyCompany.Plugins"
 });
 ```
 
-**Sample Report:**
-```markdown
-# Plugin Deployment Report: MyCompany.Plugins
-
-## Assembly Information
-- Version: 1.0.0.5
-- Isolation Mode: Sandbox
-- Last Modified: 2024-01-15 by John Doe
+Returns:
+- Assembly information
+- All registered steps
+- **Automatic validation warnings** for missing filtering attributes, images, disabled steps
 
-## Registered Steps (8 total)
+### Azure DevOps Integration
 
-### Update - Account (PreOperation, Sync, Rank 10)
-- Plugin: MyCompany.Plugins.AccountPlugin
-- Status: ✓ Enabled
-- Filtering Attributes: name, revenue, industrycode
-- Images:
-  - PreImage "Target" → Attributes: name, revenue, accountnumber
-
-## Validation Results
-
-✓ All steps are enabled
-✓ All Update/Delete steps have filtering attributes
-⚠ Warning: 2 steps without images (may need entity data)
-
-### Potential Issues
-- Account.Delete step missing PreImage - code may fail at runtime
-```
-
-### Entity Pipeline Visualization
-
-View the execution pipeline for an entity with the `entity-plugin-pipeline-report` prompt:
+Search documentation and manage work items:
 
 ```javascript
-await mcpClient.callPrompt("entity-plugin-pipeline-report", {
-  entityName: "account",
-  messageFilter: "Update"  // Optional
-});
-```
-
-**Sample Report:**
-```markdown
-# Plugin Pipeline: Account Entity
-
-## Update Message
-
-### Stage 1: PreValidation (Synchronous)
-1. [Rank 5] DataValidationPlugin.ValidateAccount
-   - Assembly: ValidationPlugins v1.0.0
-   - Filtering: name, accountnumber
-
-### Stage 2: PreOperation (Synchronous)
-1. [Rank 10] BusinessLogicPlugin.EnrichAccountData
-   - Assembly: BusinessLogic v2.0.1
-   - Filtering: revenue, industrycode
-   - Images: PreImage
-
-### Stage 3: PostOperation
-1. [Rank 10] IntegrationPlugin.SyncToERP (Async)
-   - Assembly: Integrations v3.1.0
-   - Filtering: revenue
-```
-
-## Azure DevOps Integration
-
-In addition to PowerPlatform capabilities, this MCP server provides comprehensive Azure DevOps integration for accessing wikis and work items across your organization.
-
-### Azure DevOps Configuration
-
-Set the following environment variables to enable Azure DevOps integration:
-
-```bash
-# Required: Azure DevOps organization and authentication
-AZUREDEVOPS_ORGANIZATION=your-organization-name
-AZUREDEVOPS_PAT=your-personal-access-token
-AZUREDEVOPS_PROJECTS=Project1,Project2,Project3  # Comma-separated list of allowed projects
-
-# Optional: API version (default: 7.1)
-AZUREDEVOPS_API_VERSION=7.1
-
-# Optional: Feature flags to control write/delete operations (default: false for all)
-AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE=true   # Enable create/update work items
-AZUREDEVOPS_ENABLE_WORK_ITEM_DELETE=true  # Enable delete work items
-AZUREDEVOPS_ENABLE_WIKI_WRITE=true        # Enable create/update wiki pages
-```
-
-#### Creating a Personal Access Token (PAT)
-
-1. Go to Azure DevOps → User Settings → Personal Access Tokens
-2. Click "New Token"
-3. Set required scopes:
-   - **Wiki**: `vso.wiki` (Read)
-   - **Work Items**: `vso.work` (Read) and optionally `vso.work_write` (Read & Write)
-   - **Search**: `vso.search` (Read - for wiki search)
-4. Copy the token and set it in `AZUREDEVOPS_PAT` environment variable
-
-**Security Note**: The PAT is scoped to specific permissions and projects. For maximum security, create separate PATs for read-only vs write operations.
-
-### Available Azure DevOps Tools
-
-#### Wiki Tools (5 tools)
-- `get-wikis`: List all wikis in a project
-- `search-wiki-pages`: Search wiki content across projects with highlighting
-- `get-wiki-page`: Get specific wiki page content and metadata
-- `create-wiki-page`: Create new wiki page (requires `AZUREDEVOPS_ENABLE_WIKI_WRITE=true`)
-- `update-wiki-page`: Update existing wiki page (requires `AZUREDEVOPS_ENABLE_WIKI_WRITE=true`)
-
-#### Work Item Tools (7 tools)
-- `get-work-item`: Get work item by ID with full details
-- `query-work-items`: Execute WIQL queries to find work items
-- `get-work-item-comments`: Get discussion comments for a work item
-- `add-work-item-comment`: Add comment to work item (requires `AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE=true`)
-- `update-work-item`: Update work item fields using JSON Patch (requires `AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE=true`)
-- `create-work-item`: Create new work item (requires `AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE=true`)
-- `delete-work-item`: Delete work item (requires `AZUREDEVOPS_ENABLE_WORK_ITEM_DELETE=true`)
-
-### Available Azure DevOps Prompts
-
-The server includes 4 prompts for formatted, human-readable Azure DevOps data:
-
-1. **wiki-search-results**: Search wiki pages and get formatted results with content snippets
-2. **wiki-page-content**: Get formatted wiki page with navigation context
-3. **work-item-summary**: Comprehensive work item summary with details and comments
-4. **work-items-query-report**: Execute WIQL query and get results grouped by state/type
-
-### Azure DevOps Usage Examples
-
-#### Example 1: Search Wiki Documentation
-
-```javascript
-// Search for authentication-related wiki pages
+// Search wiki
 await mcpClient.callPrompt("wiki-search-results", {
   searchText: "authentication",
-  project: "MyProject",
-  maxResults: 10
+  project: "MyProject"
 });
-```
-
-**Sample Output:**
-```markdown
-# Wiki Search Results: "authentication"
-
-**Project:** MyProject
-**Total Results:** 3
-
-## Results
-
-### 1. Setup-Guide.md
-- **Path:** /Setup/Setup-Guide
-- **Wiki:** MyProject.wiki
-- **Project:** MyProject
-- **Highlights:**
-  - Authentication can be configured using OAuth or Azure AD
-  - The authentication flow supports SAML and JWT tokens
-```
-
-#### Example 2: Get Work Item with Comments
 
-```javascript
-// Get detailed work item summary with all comments
-await mcpClient.callPrompt("work-item-summary", {
-  project: "MyProject",
-  workItemId: 12345
-});
-```
-
-**Sample Output:**
-```markdown
-# Work Item #12345: Login button not working
-
-## Details
-- **Type:** Bug
-- **State:** Active
-- **Assigned To:** John Doe
-- **Created By:** Jane Smith
-- **Created Date:** 2024-01-15T10:30:00Z
-- **Area Path:** MyProject\\Web\\Authentication
-- **Iteration Path:** Sprint 23
-- **Tags:** critical, authentication
-
-## Description
-When users click the login button on the homepage, nothing happens.
-The console shows a JavaScript error: "Cannot read property 'submit' of null"
-
-## Repro Steps
-1. Navigate to https://myapp.com
-2. Click the "Login" button in the top right
-3. Observe that nothing happens
-
-## Comments (3)
-
-### John Doe - 1/15/2024 11:00 AM
-I've investigated this issue. The problem is in the form validation logic.
-
-### Jane Smith - 1/15/2024 2:30 PM
-Created PR #456 to fix this issue.
-```
-
-#### Example 3: Query Active Bugs
-
-```javascript
-// Find all active bugs assigned to current user
+// Query work items
 await mcpClient.callPrompt("work-items-query-report", {
   project: "MyProject",
-  wiql: "SELECT [System.Id], [System.Title], [System.State] FROM WorkItems WHERE [System.WorkItemType] = 'Bug' AND [System.State] = 'Active' AND [System.AssignedTo] = @me"
+  wiql: "SELECT * FROM WorkItems WHERE [State] = 'Active' AND [Assigned To] = @me"
 });
 ```
 
-**Sample Output:**
-```markdown
-# Work Items Query Results
-
-**Project:** MyProject
-**Total Results:** 5
-
-## Active (5)
-
-- **#12345**: Login button not working
-  - Type: Bug, Assigned: John Doe
-- **#12346**: Password reset email not sent
-  - Type: Bug, Assigned: John Doe
-- **#12347**: Dashboard loads slowly
-  - Type: Bug, Assigned: John Doe
-```
+### Figma Design Extraction
 
-#### Example 4: Read Wiki Page
+Extract design specifications in AI-friendly format:
 
 ```javascript
-// Get formatted wiki page content
-await mcpClient.callPrompt("wiki-page-content", {
-  project: "MyProject",
-  wikiId: "MyProject.wiki",
-  pagePath: "/Architecture/API-Design"
+await mcpClient.invoke("get-figma-data", {
+  fileKey: "ABC123xyz",
+  depth: 3  // Limit depth for large files
 });
 ```
 
-**Sample Output:**
-```markdown
-# Wiki Page: /Architecture/API-Design
+Returns simplified JSON with:
+- Layout properties
+- Text and typography
+- Colors, fills, strokes
+- Component definitions
+- Deduplicated styles
 
-**Project:** MyProject
-**Wiki:** MyProject.wiki
-**Git Path:** Architecture/API-Design.md
+## Security & Permissions
 
-## Sub-pages
-- /Architecture/API-Design/REST-Guidelines
-- /Architecture/API-Design/Authentication
-- /Architecture/API-Design/Versioning
+All integrations are optional and can be configured independently:
 
-## Content
+**PowerPlatform:**
+- Requires Azure AD app registration
+- Uses OAuth authentication with automatic token refresh
 
-# API Design Guidelines
+**Azure DevOps:**
+- Requires Personal Access Token (PAT)
+- Write operations disabled by default (enable with environment variables)
+- Project access controlled via `AZUREDEVOPS_PROJECTS`
 
-This document describes our API design standards...
+**Figma:**
+- Requires Personal Access Token or OAuth
+- Read-only access to design files
 
-## RESTful Principles
-1. Use nouns for resources
-2. Use HTTP methods correctly...
-```
+See [SETUP.md](SETUP.md#security-best-practices) for security best practices.
 
-#### Example 5: Create Work Item (Write Operations)
+## Examples
 
-```javascript
-// Create a new bug (requires AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE=true)
-await mcpClient.invoke("create-work-item", {
-  project: "MyProject",
-  workItemType: "Bug",
-  fields: {
-    "System.Title": "Login page shows 404 error",
-    "System.Description": "After deploying v2.3, the login page returns 404",
-    "System.AssignedTo": "john@company.com",
-    "Microsoft.VSTS.TCM.ReproSteps": "1. Navigate to /login\n2. Observe 404 error",
-    "System.Tags": "critical; deployment"
-  }
-});
-```
-
-#### Example 6: Update Work Item State
+### Ask about PowerPlatform entities
 
-```javascript
-// Update work item to Resolved (requires AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE=true)
-await mcpClient.invoke("update-work-item", {
-  project: "MyProject",
-  workItemId: 12345,
-  patchOperations: [
-    {
-      "op": "add",
-      "path": "/fields/System.State",
-      "value": "Resolved"
-    },
-    {
-      "op": "add",
-      "path": "/fields/System.History",
-      "value": "Fixed in PR #456. Verified in staging environment."
-    }
-  ]
-});
 ```
-
-### WIQL Query Language
-
-Work Items queries use WIQL (Work Item Query Language), a SQL-like language:
-
-**Common WIQL Patterns:**
-
-```sql
--- Find all active bugs
-SELECT [System.Id], [System.Title]
-FROM WorkItems
-WHERE [System.WorkItemType] = 'Bug'
-  AND [System.State] = 'Active'
-
--- Find work items changed in last 7 days
-SELECT [System.Id], [System.Title], [System.ChangedDate]
-FROM WorkItems
-WHERE [System.TeamProject] = @project
-  AND [System.ChangedDate] > @today - 7
-
--- Find my active tasks in current sprint
-SELECT [System.Id], [System.Title]
-FROM WorkItems
-WHERE [System.WorkItemType] = 'Task'
-  AND [System.AssignedTo] = @me
-  AND [System.State] = 'Active'
-  AND [System.IterationPath] UNDER @currentIteration
-
--- Find user stories with specific tag
-SELECT [System.Id], [System.Title], [System.Tags]
-FROM WorkItems
-WHERE [System.WorkItemType] = 'User Story'
-  AND [System.Tags] CONTAINS 'authentication'
+User: "Tell me about the Account entity"
+AI: [uses entity-overview prompt]
+Returns comprehensive overview with key fields and relationships
 ```
 
-**WIQL Macros:**
-- `@me` - Current user
-- `@today` - Today's date
-- `@project` - Current project
-- `@currentIteration` - Current iteration path
-
-### Integration Use Cases
-
-#### Use Case 1: AI-Assisted Development with Context
-
-When working on a feature, the AI can automatically search relevant wiki documentation:
+### Build OData queries
 
 ```
-User: "I need to implement OAuth authentication for our API"
-
-AI Agent:
-1. Searches wiki: search-wiki-pages with "OAuth authentication"
-2. Finds and reads: get-wiki-page for /Architecture/Authentication/OAuth-Setup
-3. Queries related work items: query-work-items for authentication tasks
-4. Provides implementation guidance based on your organization's standards
+User: "Help me query active accounts with revenue over $1M"
+AI: [uses query-template prompt]
+Returns formatted OData query with filters
 ```
 
-#### Use Case 2: Automated Work Item Management
-
-AI can help manage work items throughout development:
+### Plugin PR reviews
 
 ```
-User: "I fixed bug #12345, mark it as resolved"
-
-AI Agent:
-1. Gets work item details: get-work-item
-2. Updates state: update-work-item to "Resolved"
-3. Adds comment: add-work-item-comment with fix details
-4. Links to PR if available
+User: "Validate the deployment of MyCompany.Plugins"
+AI: [uses plugin-deployment-report prompt]
+Returns validation report with warnings
 ```
 
-#### Use Case 3: Sprint Planning Assistant
-
-AI can analyze sprint work items and provide insights:
+### Search Azure DevOps wikis
 
 ```
-User: "Show me all active bugs in our current sprint"
-
-AI Agent:
-1. Executes WIQL query: query-work-items
-2. Groups results: work-items-query-report by priority/state
-3. Identifies blockers and dependencies
-4. Suggests prioritization based on severity
+User: "Search our wiki for OAuth documentation"
+AI: [uses wiki-search-results prompt]
+Returns formatted search results with snippets
 ```
 
-#### Use Case 4: Documentation Discovery
-
-AI can search and summarize documentation across wiki pages:
+See [USAGE.md](USAGE.md) for more examples.
 
-```
-User: "How do we handle database migrations in our projects?"
-
-AI Agent:
-1. Searches wikis: search-wiki-pages for "database migrations"
-2. Reads relevant pages: wiki-page-content for each result
-3. Summarizes best practices from your team's documentation
-4. Provides code examples from wiki pages
-```
+## Development
 
-### Security and Access Control
+### Local Development Setup
 
-The Azure DevOps integration respects your organization's security boundaries:
+```bash
+# Clone repository
+git clone <repository-url>
+cd mcp-consultant-tools
 
-1. **Project Scoping**: Only projects listed in `AZUREDEVOPS_PROJECTS` are accessible
-2. **PAT Permissions**: Access is limited to PAT scopes (read-only, read-write, etc.)
-3. **Feature Flags**: Write operations are disabled by default and must be explicitly enabled
-4. **Audit Trail**: All API operations are logged in Azure DevOps audit logs
+# Install dependencies
+npm install
 
-**Recommended Setup for Different Scenarios:**
+# Build
+npm run build
 
-**Read-Only (Documentation/Research):**
-```bash
-AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE=false
-AZUREDEVOPS_ENABLE_WORK_ITEM_DELETE=false
-AZUREDEVOPS_ENABLE_WIKI_WRITE=false
-# PAT with: vso.wiki (read), vso.work (read), vso.search (read)
+# Run locally
+node build/index.js
 ```
 
-**Developer Workflow (Read + Comment):**
-```bash
-AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE=true   # Can update work items and add comments
-AZUREDEVOPS_ENABLE_WORK_ITEM_DELETE=false # Cannot delete
-AZUREDEVOPS_ENABLE_WIKI_WRITE=false       # Cannot modify wikis
-# PAT with: vso.wiki (read), vso.work_write (read/write), vso.search (read)
-```
+### Branch Strategy
 
-**Full Access (Team Lead/Admin):**
-```bash
-AZUREDEVOPS_ENABLE_WORK_ITEM_WRITE=true
-AZUREDEVOPS_ENABLE_WORK_ITEM_DELETE=true
-AZUREDEVOPS_ENABLE_WIKI_WRITE=true
-# PAT with: vso.wiki (read/write), vso.work_write (read/write), vso.search (read)
-```
+- **`main`** - Production code (published to npm)
+- **`release/*`** - Testing before merge to main
+- **`feature/*`** - Active development
 
-## Development & Release Strategy
+**Publishing workflow:**
+1. Merge to `main`
+2. `npm version patch|minor|major`
+3. `npm publish`
+4. `git push && git push --tags`
 
-This project follows a structured branching strategy for development and releases:
+See [CLAUDE.md](CLAUDE.md) for detailed architecture and development guide.
 
-### Branch Strategy
+## Updates
 
-- **`feature/*` branches**: For active development of new features
-  - Create feature branches off `main`
-  - Develop and test changes locally
-  - Do NOT publish to npm from feature branches
-
-- **`release/*` branches**: For testing versions before release
-  - Used to test and validate changes before merging to main
-  - Do NOT publish to npm from release branches
-  - Example: `release/1.0`, `release/2.0`
-
-- **`main` branch**: Production-ready code
-  - **ONLY** publish to npm when main branch is updated
-  - Merge feature/release branches to main when ready
-  - Publishing workflow:
-    1. Merge changes to `main`
-    2. Update version: `npm version patch|minor|major`
-    3. Publish: `npm publish`
-    4. Push to GitHub: `git push && git push --tags`
+### Ensuring Latest Version
 
-### Local Development Setup
+**Using npx (recommended):**
 
-For local testing during development (feature/release branches):
+Always use `@latest` in your configuration:
 
 ```json
 {
-  "mcpServers": {
-    "mcp-consultant-tools-dev": {
-      "command": "node",
-      "args": ["/absolute/path/to/mcp-consultant-tools/build/index.js"],
-      "env": { ... }
-    }
-  }
+  "args": ["-y", "mcp-consultant-tools@latest"]
 }
 ```
 
-This allows you to test changes locally without publishing to npm.
+**Using global install:**
+
+```bash
+npm update -g mcp-consultant-tools
+```
 
 ## License
 
 MIT
+
+## Support
+
+- **Issues**: Report bugs or request features in the GitHub repository
+- **Documentation**: See docs above for complete guides
+- **Architecture**: See [CLAUDE.md](CLAUDE.md) for technical details

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-consultant-tools",
-  "version": "3.0.0",
+  "version": "3.1.0",
   "description": "MCP server providing access to PowerPlatform/Dataverse, Azure DevOps, and Figma through unified interface",
   "main": "build/index.js",
   "bin": {