MCP Consultant Tools

Modular Model Context Protocol (MCP) server providing AI-powered access to Microsoft PowerPlatform, Azure DevOps, Figma, Azure monitoring services, databases, and GitHub Enterprise.

Overview

MCP Consultant Tools is a modular monorepo with 22 independently published npm packages under the @mcp-consultant-tools organization. Install individual packages for specific integrations or the complete meta-package for everything.

Package Architecture

Core Package

Service Packages

Meta-Package

Troubleshooting: npx Cache Issues

If you experience authentication failures after switching package versions (e.g., between @beta and @latest), clear the npx cache:

npx clear-npx-cache

Then restart your MCP client. See Azure DevOps Troubleshooting for details.

Install All CLI Tools

Install every CLI tool globally with one command. Ideal for AI agents, investigation workflows, and developers who want all tools available instantly.

# macOS / Linux
curl -sL https://raw.githubusercontent.com/klemensms/mcp-consultant-tools/main/docs/cli-setup/install-cli-tools.sh | bash

# Windows (PowerShell)
irm https://raw.githubusercontent.com/klemensms/mcp-consultant-tools/main/docs/cli-setup/install-cli-tools.ps1 | iex

After installation, all 19 CLI binaries are in your PATH and ready to use. Pass credentials via --env-file .env or --mcp-server SERVER_NAME (reads from .mcp.json).

Full setup guide with agent prompt: CLI Setup Guide

Quick Start

Option 1: Individual Package (Recommended)

# Install only what you need
npx @mcp-consultant-tools/powerplatform

Option 2: Complete Package

# All integrations in one package
npx mcp-consultant-tools

MCP Client Configuration

Each package documentation includes complete setup instructions with configuration examples for Claude Desktop and VS Code. See the Documentation column in the table above.

Example (PowerPlatform with Claude Desktop):

{
  "mcpServers": {
    "powerplatform": {
      "command": "npx",
      "args": ["-y", "--package=@mcp-consultant-tools/powerplatform", "mcp-consultant-tools-powerplatform"],
      "env": {
        "POWERPLATFORM_URL": "https://yourenv.crm.dynamics.com",
        "POWERPLATFORM_CLIENT_ID": "your-client-id",
        "POWERPLATFORM_TENANT_ID": "your-tenant-id"
      }
    }
  }
}

For complete setup including authentication options, permissions, and troubleshooting, see PowerPlatform Documentation.

Option 3: CLI Usage

Every package also includes a Commander.js CLI for shell-based access to the same tools:

# Run any CLI via npx
npx --package=@mcp-consultant-tools/azure-devops mcp-ado-cli wiki list MyProject

# JSON output mode
npx --package=@mcp-consultant-tools/azure-devops mcp-ado-cli --json wiki list MyProject

# List all available CLIs
npx --package=mcp-consultant-tools mcp-tools-cli list

CLI tools use the same environment variables as MCP servers. See the CLI Binary column in the package table above.

CLI Access for AI Agents (Copy-Paste for CLAUDE.md)

If you have MCP servers configured in another repo and want agents/subagents to also use CLI tools (e.g., in hooks, subagents that don't inherit MCP connections, or shell scripts), add this to that repo's CLAUDE.md:

CLI Tools (for subagents, hooks, and scripting)

MCP servers are configured for native tool access, but CLI equivalents are also available via npx for use in subagents (which don't inherit MCP connections), hooks, and shell scripts. They use the same environment variables already configured for the MCP servers. Run npx --package=@mcp-consultant-tools/<package> <binary> --help for available commands. Common CLIs: mcp-ado-cli (Azure DevOps), mcp-pp-cli (PowerPlatform read-only), mcp-pp-custom-cli (PowerPlatform customization), mcp-pp-data-cli (PowerPlatform data), mcp-ado-admin-cli (ADO pipelines/admin), mcp-spo-cli (SharePoint), mcp-sql-cli (Azure SQL), mcp-appins-cli (Application Insights), mcp-loganalytics-cli (Log Analytics), mcp-storage-cli (Azure Storage), mcp-adf-cli (Data Factory), mcp-azure-mgmt-cli (Azure Management), mcp-ghe-cli (GitHub Enterprise), mcp-azure-b2c-cli (Azure B2C), mcp-sb-cli (Service Bus), mcp-figma-cli (Figma), mcp-rest-api-cli (REST API), mcp-teams-cli (Teams). Use --json for raw JSON output suitable for piping.

PowerPlatform Security Split

The PowerPlatform integration is split into 3 security-isolated packages:

Security is enforced through package selection - install only what you need per environment.

Documentation

Setup Guides (Start Here)

Each integration has comprehensive documentation with quick start, configuration, tool reference, and examples:

• PowerPlatform (Read-Only)
• PowerPlatform Customization
• PowerPlatform Data CRUD
• Azure DevOps
• Azure DevOps Admin
• Azure Management
• SharePoint Online
• GitHub Enterprise
• Figma
• Application Insights
• Log Analytics
• Azure SQL
• Service Bus
• Azure AD B2C
• Azure Data Factory
• REST API

Development & Technical Guides

• Development Guide (CLAUDE.md) - Architecture, patterns, contributing
• Release Process - Publishing workflow
• Migration Guide - Upgrading between major versions

Development

Build All Packages

npm install
npm run build

Build Individual Package

cd packages/powerplatform
npm run build

Local Testing

{
  "mcpServers": {
    "local-dev": {
      "command": "node",
      "args": ["/path/to/mcp-consultant-tools/packages/powerplatform/build/index.js"],
      "env": { "..." }
    }
  }
}

Links

• npm: https://www.npmjs.com/org/mcp-consultant-tools
• GitHub: https://github.com/klemensms/mcp-consultant-tools
• Issues: https://github.com/klemensms/mcp-consultant-tools/issues
• MCP Protocol: https://modelcontextprotocol.io

License

MIT License - see LICENSE for details.