Skip to content
Cloud InfrastructureAuto-generatedScore: 34

Azure Data Catalog Resource Provider MCP Server

The Azure Data Catalog Resource Provider API serves as the foundational management plane for Azure Data Catalog, a fully managed cloud-based service that acts as an enterprise-wide metadata repository and data discovery asset.

Quick Start Summary

The Azure Data Catalog Resource Provider MCP server is a Model Context Protocol bridge that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Azure Data Catalog Resource Provider API through natural language. It exposes 6 API endpoints as callable tools, such as ADCOperations_List, List catalogs in Resource Group (GET Resources), Get Azure Data Catalog service (GET Resources), and more. No authentication is required — setup takes approximately 30 seconds. The server uses STDIO transport and can be installed by running npx -y @mcp/azure-com-datacatalog. This integration is sourced from the auto Azure Data Catalog Resource Provider OpenAPI specification (v2016-03-30) and has a quality score of 34/99 (fair documentation coverage).

6Endpointstools mapped
NoneAuthopen access
34/99Qualityfair
~30 secSetupno auth

Server Details

Category
Cloud Infrastructure
Authentication
None
Endpoints
6 operations
Transport
STDIO
Spec Version
v2016-03-30
Install Command
npx -y @mcp/azure-com-datacatalog

Environment Variables

AZURE_DATA_CATALOG_RESOURCE_PROVIDER_API_KEY

Example: your_azure_data_catalog_resource_provider_api_key

Top Endpoints

GET
/providers/Microsoft.DataCatalog/operations

ADCOperations_List

GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs

List catalogs in Resource Group (GET Resources)

GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs/{catalogName}

Get Azure Data Catalog service (GET Resources)

PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs/{catalogName}

Create or Update Azure Data Catalog service (PUT Resource)

DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs/{catalogName}

Delete Azure Data Catalog Service (DELETE Resource)

Own this API?

Verify ownership of this listing to control the description, configuration details, and documentation links. Choose between free manual verification or instant premium placement.

Option 1: Free Verification

Slow manual review. Requires creating a GitHub issue with verified documentation or domain verification.

  • • Verified badge on page
  • • Standard search sorting
  • • 2-3 business days review
Start Free Claim →
Instant & Boosted

Option 2: Featured Upgrade($9/mo)

Instant verification plus premium styling, featured badges, and directory placement boost.

  • • ★ Featured star & amber highlight border
  • • Top of directory search placement
  • • Instant activation via claim token

📖 Detailed MCP Integration Guide

A technical breakdown of capabilities, agent workflows, and security/configuration best practices.

Capabilities & Use Cases
The Azure Data Catalog Resource Provider API serves as the foundational management plane for Azure Data Catalog, a fully managed cloud-based service that acts as an enterprise-wide metadata repository and data discovery asset. Provided by Microsoft, this Resource Provider (RP) enables programmatic administration of the Data Catalog service itself, distinct from the data cataloging operations (like annotating or discovering data assets) handled by the main Data Catalog REST API. Its core capabilities include the complete lifecycle management of Data Catalog instances: provisioning new catalogs within a specific resource group and subscription, retrieving details of existing catalogs, updating their configuration, and decommissioning them when no longer needed. Enterprise use cases are critical for automating infrastructure-as-code deployments, enabling DevOps teams to consistently spin up or tear down data catalogs as part of CI/CD pipelines for data platform projects. Data governance administrators use it to enforce organizational standards by scripting the creation and configuration of catalogs, ensuring all business units operate within a governed framework. It is also essential for multi-tenant or multi-project environments where automated resource provisioning is required to maintain agility and compliance.
🤖AI Agent Value
Exposing this API as tools within an AI coding assistant via the Model Context Protocol (MCP) unlocks significant productivity and governance advantages for developers and data architects. An AI agent, such as one running in Claude Desktop or Cursor, gains the ability to directly reason about and manipulate the core infrastructure of a data governance platform. This transforms the AI from a passive code-completion tool into an active operational partner. For instance, a developer can describe a desired end-state in natural language—"I need to set up a new data catalog for the European finance team with a specific naming convention"—and the AI, leveraging the MCP server, can translate this into the correct sequence of API calls: validating the resource group exists, checking for naming conflicts, and issuing the appropriate PUT request to create the catalog. This direct interaction minimizes context-switching, reduces errors from manual scripting, and ensures that infrastructure changes are executed consistently and are auditably traceable to a high-level instruction, embedding governance directly into the development workflow.
💬Example Workflows
Practical workflow examples demonstrate how an AI agent can perform dynamic, context-aware tasks. A developer can instruct the AI to "List all Data Catalogs in our production subscription and report which ones are using the legacy SKUs so we can plan a migration." The AI would orchestrate GET requests across subscriptions and resource groups, parse the responses, and generate a summarized report. Another powerful scenario involves automation: "For every new project space defined in our project registry, automatically create a corresponding Data Catalog instance in the project's designated resource group with a standardized set of tags." The AI could poll the project registry (via other connected tools), then loop through the creation process, applying consistent naming and metadata tags via the PUT/PATCH endpoints. During troubleshooting, a command like "Check the current status and configuration of the 'AnalyticsHub' catalog and compare it to our standard template" would have the AI retrieve the catalog's details and highlight deviations, acting as a configuration drift detector.
🛡️Security & Auth
While the provided endpoint list notes "None" for authentication, in practice, all interactions with the Azure Data Catalog Resource Provider API are rigorously secured through Microsoft Entra ID (formerly Azure Active Directory) and require appropriate Azure RBAC permissions. The security posture is governed by the Principle of Least Privilege: the principal (user, service principal, or managed identity) executing the API calls must be assigned a role like "Data Catalog Reader" for read operations or "Data Catalog Contributor" for create/update/delete operations at the appropriate scope (subscription or resource group). Developers configuring an MCP server for this API must ensure that the credentials (like a client secret or certificate for a service principal) used by the AI agent are stored securely in a vault, such as Azure Key Vault, and not hardcoded. Network security should also be considered, using Azure Private Link where possible to ensure traffic between the AI agent's host and Azure management endpoints remains within the Microsoft backbone network, mitigating public internet exposure risks. Regular auditing of the operations performed by the AI agent through Azure Activity Logs is a mandatory best practice to maintain compliance and security oversight.

Similar APIs

Other APIs in the Cloud Infrastructure category.

Related MCP Server Integrations

Supabase API MCP Setup

Manage Supabase projects, databases, authentication, and storage through your AI agent.

Cloud InfrastructureConfigure →

Cloudflare API MCP Setup

Manage Cloudflare DNS, CDN, Workers, and security settings through your AI agent.

Cloud InfrastructureConfigure →

Vercel API MCP Setup

Deploy projects, manage domains, and monitor deployments through your AI agent.

Cloud InfrastructureConfigure →

DigitalOcean API MCP Setup

The DigitalOcean API is a comprehensive, RESTful interface provided by DigitalOcean, a leading cloud infrastructure provider focused on simplifying cloud computing for developers, startups, and enterprises. It serves as the programmatic backbone for managing the entire DigitalOcean ecosystem, enabling users to provision, configure, and control cloud resources such as Droplets (virtual private servers), Kubernetes clusters, managed databases, networks, storage volumes, and application platforms. Core capabilities include full lifecycle management of these resources, from creation and scaling to monitoring and deletion, mirroring the functionality available in the DigitalOcean control panel. Its primary use cases range from automating infrastructure setup for CI/CD pipelines and enabling infrastructure-as-code practices to supporting dynamic application scaling and resource optimization for SaaS products, e-commerce sites, and development environments. The API is designed for both developers seeking to automate their cloud operations and businesses that require programmable, scalable cloud infrastructure without the complexity of larger hyperscale providers.

Cloud InfrastructureConfigure →

Access Analyzer MCP Setup

The AWS Identity and Access Management Access Analyzer API provides a powerful, policy-as-code service that automatically identifies resources accessible from outside your AWS account or organization. At its core, the service continuously evaluates resource-based policies—such as Amazon S3 bucket policies, AWS Identity and Access Management (IAM) roles, Amazon KMS key policies, and AWS Lambda function policies—using logic-based reasoning to determine which resources grant access to unknown external principals. Its primary use case is for security and compliance teams within enterprises to proactively detect unintended data exposure, enforce least privilege principles, and audit cross-account and cross-service access. The API endpoints allow programmatic control to create, configure, and query analyzers, manage archive rules for storing findings, and generate custom policy documents, making it a foundational tool for automating cloud security posture management at scale.

Cloud InfrastructureConfigure →