Skip to main content

MCP Server (AI) Overview

Cloudaware MCP (Metadata & Query Proxy) Server provides a secure AI data layer on top of your Cloudaware CMDB and Google BigQuery Export Project.

MCP Server (AI) enables LLM-based tools such as ChatGPT, Claude, GitHub Copilot, and other AI assistants to:

  • Understand the Cloudaware CMDB as a structured data model.
  • Explore object types, fields, and relationships.
  • Execute SQL queries against your BigQuery export.

This allows AI assistants to navigate infrastructure data, answer questions about resources and dependencies, and generate code and reports based on real Cloudaware data.

Key Capabilities​

CMDB as a Self-Describing Graph​

MCP exposes the Cloudaware CMDB as a self-describing graph of objects, fields, and relationships. Any compatible LLM can:

  • Discover object types and their API names.
  • Inspect fields, labels, and data types.
  • Understand how objects are related in the relationship graph.
  • Reason about infrastructure without navigating the Cloudaware UI.

Under the hood, tools such as search_types, search_fields, get_relationship_graph, analyze_field, and execute_query enable AI agents to follow a "discover first, query later" pattern.

Direct SQL Access to BigQuery Export​

MCP provides AI tools with controlled SQL execution against your Cloudaware BigQuery Export Project. AI assistants can:

  • Explore datasets and tables.
  • Join infrastructure and cost or usage data.
  • Build custom reports and dashboards.
  • Support engineering and analytics workflows.

Queries are executed with the execute_query tool against your existing Export Project and SObjects dataset.

Bring Your Own LLM​

MCP is model-agnostic and integrates with:

  • ChatGPT
  • Claude Code and Claude.ai
  • GitHub Copilot
  • Gemini CLI
  • LM Studio and local models
  • Internal chatbots and AI assistants
  • Other MCP-enabled tools

Your teams can keep using their existing IDEs, CLIs, and internal assistants while MCP makes Cloudaware data available within those tools.

Enterprise-Grade Security​

MCP is designed as a read-only execution layer operating under the authenticated identity.

  • AI can read metadata and execute queries only within that identity's permissions. MCP does not introduce additional privileges.
  • Access is scoped to the selected Export Project and SObjects dataset.
  • MCP inherits the same permissions as the authenticated user for HTTP access through Google OAuth 2.0, or the configured service account for local execution.
  • All access respects existing BigQuery IAM permissions.

If a user does not have access to a dataset in BigQuery, MCP will not expose it to AI tools.

Use Cases​

AI Resource Finder​

MCP enables AI-driven resource discovery without manual UI searches. Engineers, FinOps analysts, and architects can ask an AI assistant to:

  • Find all EBS volumes matching a specific pattern.
  • List S3 buckets in selected accounts with their key properties.
  • Show all resources that match defined filters.

AI Navigator for CMDB​

MCP makes the CMDB self-explanatory for onboarding, troubleshooting, and in-product AI assistance. Users can ask an AI assistant to:

  • Explain what a specific object or field represents.
  • Show where a given CI is stored.
  • Find objects related to a service, account, VPC, or environment.

This is the backend capability for any AI helper embedded into the Cloudaware UI.

Inventory Research and Data Exploration​

With MCP, an LLM can explore the CMDB structure, explain objects and values, and guide engineers through the data without requiring them to first build complex list views or reports.

Example prompts include:

  • Analyze inventory and show what exists for a specific application.
  • Compare sets of resources under given conditions.
  • Suggest where to look for a CI or attribute.

Developer Automation Accelerator​

Before MCP, developers typically needed to:

  • Study CMDB SObjects and their relationships.
  • Build ETL jobs or many API calls.
  • Manually discover which fields to use in scripts.

With MCP, an AI assistant can:

  • Generate Python scripts that interact with Cloudaware APIs or BigQuery.
  • Select the correct objects and fields based on metadata.
  • Compose queries and joins that follow the actual relationship graph.

This reduces the time needed to build automation from weeks or months of discovery to minutes of interaction with an AI tool.

Auto-Documentation and CMDB Intelligence​

MCP enables AI-driven documentation of your data model. AI assistants can:

  • Document structures of CMDB objects.
  • Describe field purpose and semantics.
  • Build dependency graphs between services and resources.

This is especially valuable for complex, long-running environments and for onboarding new team members.

Explore MCP Server (AI)​

Refer to Configuration for setup instructions, supported HTTP transport modes, and system requirements.