convez.ai
MCP ServerIntegração & APIsAvançado
klemensms

MCP Consultant Tools

klemensms/mcp-consultant-tools

MCP servers modulares para ecossistema Microsoft, Azure e integrações enterprise

Ver no GitHub
InicialPluginScore · de 0 a 100

Suite modular de servidores MCP com 22 pacotes npm independentes para integração com PowerPlatform, Azure DevOps, Azure, SharePoint, Figma, GitHub Enterprise e mais. Oferece proteção de PII com pipeline de 4 camadas e auditoria tamper-evident para ambientes produtivos.

Instalação

$npx convez-ai klemensms/mcp-consultant-tools

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 1 mês
Versão
v33.0.0
Issues abertas
0
Contribuidores
1

Casos de uso

  • Automatizar operações em PowerPlatform/Dataverse com proteção de dados sensíveis
  • Gerenciar Azure DevOps (wikis, work items, PRs, builds) via IA
  • Consultar e monitorar recursos Azure (Functions, App Services, Key Vault, SQL)
  • Extrair dados de design do Figma e sincronizar com sistemas
  • Gerenciar SharePoint Online e GitHub Enterprise programaticamente

Veredito

Solução enterprise-grade robusta com arquitetura modular bem pensada e segurança nativa (PII protection opt-in). Excelente para consultores e times que operam em stacks Microsoft/Azure complexos. Requer conhecimento intermediário-avançado de TypeScript e arquitetura MCP para customizações.

README

A tradução para o português deste README ainda está na fila.

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.

npm version License: MIT

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.

PII protection (v32): A 4-layer redaction pipeline is built into powerplatform-data, azure-devops, azure-sql, rest-api, and azure-b2c to keep personal data from reaching the US-hosted LLM during MCP tool calls against client production environments. It is opt-in — off by default; enable it per server with PII_PROTECTION=true. See docs/documentation/pii-protection.md.

  • PII audit logging (opt-in): when enabled with MCP_AUDIT_LEVEL=lean|full, every Dataverse MCP tool call produces a tamper-evident audit record (Phase A — local file; Phase B — central sync follows).

Package Architecture

Core Package

PackageDescription
@mcp-consultant-tools/coreShared utilities, MCP helpers, audit logging

Service Packages

PackageIntegrationToolsCLI BinaryDocumentation
powerplatform-coreShared PowerPlatform services (internal)N/AN/A—
powerplatformPowerPlatform/Dataverse (Read-Only)49mcp-pp-cliSetup & Usage
powerplatform-customizationPowerPlatform Schema Changes85mcp-pp-custom-cliSetup & Usage
powerplatform-dataPowerPlatform Data CRUD14mcp-pp-data-cliSetup & Usage
azure-devopsAzure DevOps Wikis, Work Items, PRs, Builds, Test Runs65mcp-ado-cliSetup & Usage
azure-devops-adminAzure DevOps Pipelines, Service Conns, Pools66mcp-ado-admin-cliSetup & Usage
azure-managementAzure ARM API (Functions, App Services, Key Vault, SQL, Monitoring)31mcp-azure-mgmt-cliSetup & Usage
sharepointSharePoint Online16-22mcp-spo-cliSetup & Usage
github-enterpriseGitHub Enterprise22mcp-ghe-cliSetup & Usage
figmaFigma Design Extraction4mcp-figma-cliSetup & Usage
application-insightsApplication Insights10mcp-appins-cliSetup & Usage
log-analyticsLog Analytics13mcp-loganalytics-cliSetup & Usage
1password1Password Vault & Item Management21mcp-op-cliSetup & Usage
azure-sqlAzure SQL Database20mcp-sql-cliSetup & Usage
service-busAzure Service Bus8mcp-sb-cliSetup & Usage
azure-b2cAzure AD B2C11mcp-azure-b2c-cliSetup & Usage
azure-storageAzure Blob, Files, Queue, Table Storage47mcp-storage-cliSetup & Usage
azure-data-factoryAzure Data Factory24mcp-adf-cliSetup & Usage
fabricMicrosoft Fabric (Workspaces, Capacities, Items, Shortcuts, Domains, Admin)27mcp-fabric-cliSetup & Usage
rest-apiGeneric REST API (OAuth2)4mcp-rest-api-cliSetup & Usage
teamsMicrosoft Teams messaging7mcp-teams-cliSetup & Usage

Meta-Package

PackageDescription
mcp-consultant-toolsComplete package with all integrations

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.

Troubleshooting: npm error code E401 (Unable to authenticate)

Symptom — an MCP server fails to start and the stderr tail shows:

npm warn Unknown project config "always-auth". This will stop working in the next major version of npm.
npm error code E401
npm error Unable to authenticate, your authentication token seems to be invalid.
npm error To correct this please try logging in again with: npm login

This is npm failing to authenticate to a package registry — not the MCP server crashing. It happens on machines (common at consulting shops / corporate setups) where npm's default registry is a private feed — Azure DevOps Artifacts, GitHub Packages, or an internal Verdaccio/Nexus proxy — usually with always-auth=true and a PAT that has expired. With always-auth on, npm tries to authenticate even when fetching the public @mcp-consultant-tools/* packages, and the dead token makes it bomb out before npx ever runs. The always-auth warning is the giveaway.

Fix (recommended): pin the scope to the public npm registry

Tell npm that the @mcp-consultant-tools scope always comes from public npm, regardless of the default registry. This is non-destructive — it leaves the private feed working for everything else.

  1. Open (or create) your user-level .npmrc:
    • Windows: C:\Users\<your-username>\.npmrc
    • macOS / Linux: ~/.npmrc
  2. Add this line:
    @mcp-consultant-tools:registry=https://registry.npmjs.org/
    
  3. Verify (run from any directory):
    npm config get @mcp-consultant-tools:registry
    # → should print: https://registry.npmjs.org/
    
    npm view @mcp-consultant-tools/azure-devops@beta version
    # → should print a version (e.g. 32.0.0-beta.2), NOT "npm error code E401"
    
  4. In your MCP client, reconnect the server (in Claude Code: /mcp → reconnect, or restart the session). The first launch is slow while npx fetches the package, then it connects.

Diagnosing / alternative fixes

  • Confirm the diagnosis — force the public registry for one call:
    npx --registry=https://registry.npmjs.org -y --package=@mcp-consultant-tools/PACKAGE BINARY --help
    
    If that works, it's 100% an .npmrc / registry-config issue.
  • Inspect the offending config — cat ~/.npmrc (and any project-level .npmrc in the working directory). Look for: always-auth=true, a registry=https://... pointing at a private feed, //pkgs.dev.azure.com/...:_authToken=... (expired PAT), or a stray @mcp-consultant-tools:registry= pointing somewhere other than public npm.
  • Check the active default registry — npm config get registry must return https://registry.npmjs.org/. If it returns a private feed and the scope pin above isn't an option, that's the root cause.
  • Stored / env-var tokens — npm logout to clear stored tokens, then retry. Also check env | grep -i npm — NPM_CONFIG_REGISTRY, NPM_TOKEN, NODE_AUTH_TOKEN override .npmrc.

npx clear-npx-cache does not help here — the cache isn't the problem, the registry config is.


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 21 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-fabric-cli (Microsoft Fabric), mcp-rest-api-cli (REST API), mcp-teams-cli (Teams), mcp-audit-cli (audit log verify/quarantine/search). Use --json for raw JSON output suitable for piping.

PowerPlatform Security Split

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

PackagePurposeProduction-Safe?
powerplatformRead-only access✅ YES
powerplatform-customizationSchema changes⚠️ Dev/config only
powerplatform-dataData CRUD⚠️ Operational use

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:

Development & Technical Guides

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

License

MIT License - see LICENSE for details.

Ver o original no GitHub

Bom para

Relacionados