What is Osdu Mcp Server

The osdu-mcp-server is a Model Context Protocol (MCP) server that facilitates communication between AI assistants and the OSDU platform, enabling access to various services such as search, data management, and schema operations.

Use cases

Use cases for the osdu-mcp-server include automating data retrieval and management tasks, enhancing search functionalities for large datasets, and enabling AI-driven insights and analytics within the OSDU ecosystem.

How to use

To use the osdu-mcp-server, developers can integrate it into their AI applications, allowing the AI to interact with OSDU services via the MCP protocol. Detailed documentation is available for setting up and utilizing the server effectively.

Key features

Key features of the osdu-mcp-server include AI-driven development capabilities, support for multiple AI agents, comprehensive documentation for AI integration, and the ability to perform various operations on the OSDU platform.

Where to use

The osdu-mcp-server is primarily used in industries that leverage AI for data management and analysis, particularly in sectors like energy, geosciences, and other data-intensive fields that utilize the OSDU platform.

OSDU MCP Server

A Model Context Protocol (MCP) server that provides AI assistants with access to OSDU platform capabilities.

Purpose

This server enables AI assistants to interact with OSDU platform services including search, data management, and schema operations through the MCP protocol.

AI-Driven Development

This project follows an AI-driven development workflow:

• 🤖 Built with AI - Developed using Claude Code and GitHub Copilot
• 📋 AI Task Assignment - Issues labeled with copilot are automatically assigned
• 📚 AI-Friendly Documentation - Comprehensive guides for AI agents in CLAUDE.md and .github/copilot-instructions.md
• 🔄 Multi-Agent Orchestration - Different AI agents handle different tasks based on their strengths

See our Case Study for insights on building quality code with AI agents.

Documentation

• Project Brief
• Project Requirements
• Architecture Overview
• Architecture Design Decisions

Installation

# Clone the repository
git clone <repository-url>
cd osdu-mcp-server

# Install using uv (recommended)
uv sync
uv pip install -e '.[dev]'

Configuration

To utilize this MCP server directly in other projects either use the buttons to install in VSCode, edit the .mcp.json file directory.

Clients tend to have slightly different configurations

To use the OSDU MCP Server, configure it through your MCP client’s configuration file:

{
  "mcpServers": {
    "osdu-mcp-server": {
      "type": "stdio",
      "command": "uv",
      "args": [
        "run",
        "osdu-mcp-server"
      ],
      "env": {
        "OSDU_MCP_SERVER_URL": "https://your-osdu.com",
        "OSDU_MCP_SERVER_DATA_PARTITION": "your-partition",
        "AZURE_CLIENT_ID": "your-client-id",
        "AZURE_TENANT_ID": "your-tenant"
      }
    }
  }
}

Domain Configuration

Critical for ACL Format: OSDU deployments use different data domain formats for Access Control Lists (ACL). Configure your data domain to avoid ACL format errors:

Data Domain Examples:

• Standard OSDU: contoso.com (default)
• Microsoft OSDU: dataservices.energy
• Microsoft Internal: msft-osdu-test.org

Data Domain Detection Methods:

1. Environment Variable (Recommended): Set OSDU_MCP_SERVER_DOMAIN
2. Use Entitlements Tool: Run entitlements_mine() to see your group format
3. Check with Administrator: Ask your OSDU administrator for the correct data domain

Important: The data domain is the internal OSDU data system domain used in ACL group emails, not the FQDN from your server URL.

If not set, the server will attempt to extract the domain from your server URL. For more guidance, use the MCP resource: ReadMcpResourceTool(server="osdu-mcp-server", uri="file://acl-format-examples.json").

Authentication Methods

Authentication is handled via the Azure CLI by default. You must be logged in using az login before running the server:

To enable Service Principal authentication, add the optional AZURE_CLIENT_SECRET environment variable:.

Write Operations

Write operations (create, update) for any service are disabled by default, you must explicitly enable them:

Delete Operations

Delete and purge operations are separately controlled and disabled by default:

This dual protection allows you to enable data creation and updates while maintaining strict control over destructive operations.

Complete Configuration Example

Here’s a complete .mcp.json configuration example with all common environment variables:

{
  "mcpServers": {
    "osdu-mcp-server": {
      "type": "stdio",
      "command": "uv",
      "args": [
        "run",
        "osdu-mcp-server"
      ],
      "env": {
        "OSDU_MCP_SERVER_URL": "https://team.internal.msft-osdu-test.org",
        "OSDU_MCP_SERVER_DATA_PARTITION": "opendes",
        "OSDU_MCP_SERVER_DOMAIN": "contoso.com",
        "OSDU_MCP_ENABLE_WRITE_MODE": "true",
        "OSDU_MCP_ENABLE_DELETE_MODE": "true",
        "AZURE_CLIENT_ID": "your-client-id",
        "AZURE_TENANT_ID": "your-tenant-id",
        "AZURE_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Logging Configuration

The MCP server uses structured JSON logging that follows ADR-016. By default, logging is disabled due to verbosity. You can enable it by setting:

Valid logging levels: DEBUG, INFO, WARNING, ERROR, CRITICAL

Usage

Health Check

osdu:health_check

This returns the health status of your OSDU platform, checking authentication and the availability of all services (storage, search, legal, schema, file, workflow, entitlements, and dataset).

Available Capabilities

Prompts

• list_mcp_assets: Comprehensive overview of all server capabilities with usage examples and quick start guidance
• guide_search_patterns: Search pattern guidance for OSDU operations with Elasticsearch syntax examples

Tools

Foundation

• health_check: Check OSDU platform connectivity and service health

Partition Service

• partition_list: List all accessible OSDU partitions
• partition_get: Retrieve configuration for a specific partition
• partition_create: Create a new partition (write-protected)
• partition_update: Update partition properties (write-protected)
• partition_delete: Delete a partition (write-protected)

Entitlements Service

• entitlements_mine: Get groups for the current authenticated user

Legal Service

• legaltag_list: List all legal tags
• legaltag_get: Get specific legal tag
• legaltag_get_properties: Get allowed property values
• legaltag_search: Search legal tags with filters
• legaltag_batch_retrieve: Get multiple tags at once
• legaltag_create: Create new legal tag (write-protected)
• legaltag_update: Update legal tag (write-protected)
• legaltag_delete: Delete legal tag (delete-protected)

Schema Service

• schema_list: List available schemas with optional filtering
• schema_get: Retrieve complete schema by ID
• schema_search: Advanced schema discovery with rich filtering and text search
• schema_create: Create a new schema (write-protected)
• schema_update: Update an existing schema (write-protected)

Search Service

• search_query: Execute search queries using Elasticsearch syntax
• search_by_id: Find specific records by ID
• search_by_kind: Find all records of specific type

Storage Service

• storage_create_update_records: Create or update records (write-protected)
• storage_get_record: Get latest version of a record by ID
• storage_get_record_version: Get specific version of a record
• storage_list_record_versions: List all versions of a record
• storage_query_records_by_kind: Get record IDs of a specific kind
• storage_fetch_records: Retrieve multiple records at once
• storage_delete_record: Logically delete a record (delete-protected)
• storage_purge_record: Permanently delete a record (delete-protected)