📘 Cloudamize MCP Server (End User User & Integration Guide)

🌐 Overview

The Cloudamize MCP Server is a containerized MCP gateway that exposes Cloudamize APIs to AI tools it connects Cloudamize to AI assistants, AI agents, and large-scale agentic systems through the Model Context Protocol (MCP).

It enables external systems to securely access and use Cloudamize data such as:

📦 Migration Plans

“What migration plans do I have for AWS?”
“Show my active plans”

💰 Cost (TCO) Insights

“What is the total cost of my migration plan?”
“TCO for plan 12345”

🖥 Infrastructure

“Summarize my infrastructure”

💡 Workload Recommendations

“What instance recommendations do you suggest?”

🧭 Migration grouping and planning intelligence

“How are servers grouped for migration?”

Cloudamize MCP allows AI systems and agentic workflows to programmatically retrieve and act on Cloudamize assessment and migration data.

🔗 Hosted MCP Endpoint

CODE

https://mcp.cloudamize.com

🧠 Supported Consumers

Cloudamize MCP can be used by:

🤖 AI Assistants

Cursor
Claude Desktop
IDE copilots

⚙️ AI Agents

Custom automation agents
Workflow agents
Internal orchestration tools

🏗️ Agentic Systems (Enterprise Scale)

AWS Transform
Kiro agent
Internal enterprise migration agents
Multi-step autonomous workflows
Cloud optimization pipelines

💡 What MCP enables

AI systems can:

Query Cloudamize assessment data
Retrieve migration plans
Generate cost and TCO insights
Fetch workload recommendations
Understand migration grouping strategies
Use data inside multi-step automated workflows

🔁 Typical Usage Flow

System requests migration or assessment data
MCP server fetches Cloudamize data securely
Response is returned in structured format
AI agent/assistant uses it in reasoning or automation

🌐 Access Modes

Mode	Endpoint	Use Case
🌍 Hosted MCP	https://mcp.cloudamize.com	Recommended if wanted use in SaaS style.
🐳 Local MCP	http://localhost:8080	Restricted / offline environments

❤️ Health check

CODE

GET /healthz

Response:

CODE

204 No Content

📡 MCP endpoint

CODE

POST https://mcp.cloudamize.com/

or local:

CODE

POST http://localhost:8080/mcp

🔐 Authentication Methods

MCP supports both authentication models:

1️⃣ Bearer Token (Recommended)

CODE

Authorization: Bearer <access_token>

2️⃣ API Key

CODE

X-API-Key: <api_key>
X-Customer-Id: <customer_id>

🔑 Generate Access Token

CODE

API_USER="your-email@cloudamize.com"
API_PASS="your-password"

AUTH=$(printf "%s:%s" "$API_USER" "$API_PASS" | base64)

TOKEN=$(curl --silent \
  --location 'https://precloud-api.cloudamize.com/auth/token?termsAccepted=true' \
  --header "Authorization: Basic $AUTH" \
  | tr -d '\n' \
  | cut -d'"' -f4)

echo "$TOKEN"

🧪 Example MCP Call

CODE

curl --location 'https://mcp.cloudamize.com/mcp' \
--header "Authorization: Bearer $TOKEN" \
--header "Content-Type: application/json" \
--data '{}'

⚠️ Troubleshooting

Issue	Meaning	Fix
No data returned	MCP not connected	Check integration
Unauthorized	Token expired	Regenerate token
Wrong plan	Invalid ID	Fetch plan list first

🔐 Security Principles

Tokens must not be shared or embedded in code
Do not store credentials in chat
Use API keys or tokens securely

🌐 Overview

The Cloudamize MCP Server connects your AI assistant (Cursor, Claude Desktop, etc.) to your Cloudamize environment.

Hosted at:

CODE

https://mcp.cloudamize.com

It allows you to ask questions in natural language and get insights from your Cloudamize data.

💡 What you can do

You can ask:

📦 Migration Plans

“What migration plans do I have for AWS?”
“Show my active plans”

💰 Cost (TCO)

“What is the total cost of my migration plan?”
“TCO for plan 12345”

🖥 Infrastructure

“Summarize my infrastructure”

💡 Recommendations

“What instance recommendations do you suggest?”

🧭 Grouping

“How are servers grouped for migration?”

🔁 How to use (simple flow)

Ask:
Show my migration plans
Select plan ID/name
Ask deeper:
Give TCO for this plan on AWS

🌐 Access modes

Mode	Endpoint	Use Case
Hosted MCP	https://mcp.cloudamize.com	Recommended
Local MCP	http://localhost:8080	Restricted environments

🔐 Authentication

You can use either:

1️⃣ Bearer Token (Recommended)

CODE

Authorization: Bearer <access_token>

2️⃣ API Key

CODE

X-API-Key: <api_key>
X-Customer-Id: <customer_id>

🔑 Generate Token

CODE

API_USER="your-email@cloudamize.com"
API_PASS="your-password"

AUTH=$(printf "%s:%s" "$API_USER" "$API_PASS" | base64)

TOKEN=$(curl --silent \
  --location 'https://precloud-api.cloudamize.com/auth/token?termsAccepted=true' \
  --header "Authorization: Basic $AUTH" \
  | tr -d '\n' \
  | cut -d'"' -f4)

echo "$TOKEN"

🧪 Example request

CODE

curl --location 'https://mcp.cloudamize.com/mcp' \
--header "Authorization: Bearer $TOKEN" \
--header "Content-Type: application/json" \
--data '{}'

⚠️ Troubleshooting

Issue	Fix
No data	Check MCP connection
Unauthorized	Re-login / refresh token
Wrong plan	Verify plan ID

🔐 Security

Data stays within your Cloudamize account
No external data is used
Do not share tokens
Do not store credentials in chat
Use API keys or tokens securely

🧭 Decision Guide

👉 Use Hosted MCP if:

You want zero setup
Your AI tool supports remote MCP URLs
You prefer managed infrastructure

👉 Use Local MCP if:

Remote MCP is blocked
You need offline / internal network support
You want full control