AWS Service Catalog MCP Server Integration Guide
Section A: Quick Answer & Architectural Summary
The AWS Service Catalog Model Context Protocol (MCP) integration bridges AI coding assistants to the AWS Service Catalog cloud infrastructure API. It exposes 10 validated endpoint operations as callable tools for Claude Desktop, Cursor, and VS Code. Configuration is managed via hosted registry at /config/amazonaws-com-servicecatalog.json or local stdio bridge execution. Operates with zero authentication credentials out of the box. Contains 10 mutating operations (POST/PUT/DELETE); user confirmation is recommended before triggering write operations.
MCPBridge Editorial Verdict: AWS Service Catalog
AI coding workflows requiring programmatic access to AWS Service Catalog (Cloud Infrastructure) endpoints
Low (1-2 mins)
Zero Authentication Required
Automated Spec Tracking
Claude Desktop, Cursor IDE, VS Code (Cline), Zed Editor
Read & Mutating endpoints; client confirmation and least-privilege token recommended
MCPBridge rates AWS Service Catalog as a standardized OpenAPI-to-MCP bridge providing structured tool definitions across 10 endpoints.
Technical Overview & Protocol Integration
AWS Service Catalog is a managed service provided by Amazon Web Services (AWS) that enables organizations to create, manage, and govern catalogs of approved IT services, such as virtual machines, databases, storage buckets, and complex multi-tier applications. At its core, the service provides a centralized framework for enterprise teams, including cloud administrators and platform engineers, to curate standardized, secure, and compliant cloud resources for consumption by developers, data scientists, and business units. This ensures that the cloud resources provisioned within an organization adhere to best practices for security, cost control, and operational efficiency, effectively balancing the need for speed with the imperative of governance. Typical use cases include enforcing standardized AMI versions for EC2 instances, managing a menu of pre-configured Amazon RDS database templates with specific parameter groups, and deploying entire application stacks via AWS CloudFormation templates while controlling access and tracking usage.
When the AWS Service Catalog API is exposed as a set of tools via the Model Context Protocol (MCP) to an AI coding assistant like Claude Desktop, Cursor, or Cline, it transforms the AI from a code generator into a dynamic cloud operations partner. The AI agent gains real-time, programmatic awareness of and control over the organization's approved service catalog. This integration is particularly powerful for accelerating development workflows and automating governance. A developer can instruct the AI to discover available products and their versions before writing infrastructure-as-code, ensuring they reference valid artifacts. The AI can automate the complex setup of a new portfolio, including associating the correct launch constraints and access controls, by translating a high-level request into a precise sequence of API calls. It can also facilitate continuous compliance by querying constraints and associations to verify a product configuration against organizational policies before deployment.
Practical workflow examples demonstrate significant productivity gains. A developer could instruct the AI agent with a command like, "Help me deploy a new, secure S3 bucket for our project. First, check the service catalog for our company-approved S3 bucket product and list its available versions." The AI would use the SearchProducts and DescribeProduct actions to retrieve this information. Subsequently, a command such as "Create a new portfolio named 'Data Science Team Services' and give the IAM role 'DataScienceLead' full access to it" would trigger the AI to orchestrate calls to CreatePortfolio and AssociatePrincipalWithPortfolio. For managing updates, a user could ask, "The 'Windows Server 2022' product in the 'Infrastructure Base' portfolio has a new provisioning artifact. Update the launch constraint to use the latest IAM role." The AI would then sequentially execute UpdateProvisioningArtifact and UpdateConstraint to implement the change safely.
Crucially, while the API endpoint list itself does not embed authentication, all requests to the AWS Service Catalog API must be authenticated and authorized using AWS Identity and Access Management (IAM) credentials. Developers integrating this API via an MCP server must adhere to the principle of least privilege. This means creating a dedicated IAM role or user with permissions scoped only to the specific Service Catalog actions required for the AI agent's tasks. For example, an AI agent used for portfolio setup should not have permissions for TerminateProvisionedProduct. The MCP server's connection to AWS must use secure credential management, typically leveraging environment variables or a secured secret store to provide the necessary access key and secret key to the SDK calls. All API traffic should be conducted over HTTPS (which is the default for AWS service endpoints), and organizations should enable AWS CloudTrail logging to audit all actions performed via the API, creating a traceable record of AI-driven operations.
By translating the OpenAPI 3.0 specification for AWS Service Catalog into native Model Context Protocol (MCP) tool definitions, developers and AI agents gain programmatic access to endpoints over stdio or HTTP transports. Every endpoint is translated into a discrete tool payload complete with input argument validation, parameter descriptions, and return type definitions.
2. Technical Specifications Matrix
System Specifications
| API Name | AWS Service Catalog |
| Slug Identifier | amazonaws-com-servicecatalog |
| Category | Cloud Infrastructure |
| Auth Method | None Required |
| Endpoint Count | 10 tools mapped |
| Spec Version | OpenAPI v2015-12-10 |
| Transport Type | STDIO |
| Publisher Source | auto |
3. Multi-Client Installation Matrix
Copy and paste these pre-formatted JSON snippets into your MCP client configuration files.
Claude Desktop
Add to claude_desktop_config.json
{
"mcpServers": {
"amazonaws-com-servicecatalog": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/amazonaws.com/servicecatalog/2015-12-10/openapi.json"
],
"env": {
"AWS_SERVICE_CATALOG_API_KEY": "your_aws_service_catalog_api_key"
}
}
}
}Cursor IDE
Settings → MCP Servers → Add Hosted Config
{
"mcpServers": {
"amazonaws-com-servicecatalog": {
"url": "https://mcpbridge.org/config/amazonaws-com-servicecatalog.json"
}
}
}Saves as .cursor/mcp.json in the download. Move it to your project root.
VS Code / Cline
Use with MCP extension config
{
"mcpServers": {
"amazonaws-com-servicecatalog": {
"url": "https://mcpbridge.org/config/amazonaws-com-servicecatalog.json"
}
}
}4. Security Architecture & Credentials Reference
Key parameters and credential variable mappings for AWS Service Catalog.
Security Considerations & Sandbox Guidance: AWS Service Catalog
Authorization credential isolation, least privilege boundaries, and container sandboxing options.
None Required
Read & Mutating Operations
Local MCP bridge process making outbound HTTPS requests to upstream API
Isolation & Principle of Least Privilege
Ensure outbound network access to the API endpoint is permitted. Use restricted API tokens with minimal read/write scopes.
Actionable Operational Guidelines
- Verify network firewall rules allow outbound traffic to upstream API endpoints.
- Review arguments for mutating endpoints (/#X-Amz-Target=AWS242ServiceCatalogService.AcceptPortfolioShare, /#X-Amz-Target=AWS242ServiceCatalogService.AssociateBudgetWithResource, /#X-Amz-Target=AWS242ServiceCatalogService.AssociatePrincipalWithPortfolio) before execution.
- Apply token rate limits and monitor usage in your provider dashboard to prevent unexpected quota consumption.
| Variable Name | Required | Example Value |
|---|---|---|
| AWS_SERVICE_CATALOG_API_KEY | REQUIRED | your_aws_service_catalog_api_key |
5. Endpoints & Tool Schemas Matrix
Search and inspect the 10 tool signatures mapped from OpenAPI.
Executable Code Integration Examples
Call AWS Service Catalog endpoints via cURL, TypeScript, or Python REST SDKs.
curl -X POST "https://api.apis.guru/v2/specs/amazonaws.com/servicecatalog/2015-12-10/#X-Amz-Target=AWS242ServiceCatalogService.AcceptPortfolioShare" \ -H "Content-Type: application/json" \ # No auth required
Concrete Real-World Use Cases for AWS Service Catalog
Practical multi-step agentic workflows and prompt directives demonstrating concrete developer outcomes.
Automated Contextual Workflow Integration
Practical workflow examples demonstrate significant productivity gains. A developer could instruct the AI agent with a command like, "Help me deploy a new, secure S3 bucket for our project. First, check the service catalog for our company-approved S3 bucket product and list its available versions." The AI would use the `SearchProducts` and `DescribeProduct` actions to retrieve this information. Subsequently, a command such as "Create a new portfolio named 'Data Science Team Services' and give the IAM role 'DataScienceLead' full access to it" would trigger the AI to orchestrate calls to `CreatePortfolio` and `AssociatePrincipalWithPortfolio`. For managing updates, a user could ask, "The 'Windows Server 2022' product in the 'Infrastructure Base' portfolio has a new provisioning artifact. Update the launch constraint to use the latest IAM role." The AI would then sequentially execute `UpdateProvisioningArtifact` and `UpdateConstraint` to implement the change safely.
- AI assistant inspects prompt context and selects relevant tool
- Validates parameter payload against OpenAPI JSON Schema
- Executes tool call and formats structured API response
Automated Mutation & Resource Creation
Execute state changes and create records through POST operations like "/#X-Amz-Target=AWS242ServiceCatalogService.AcceptPortfolioShare" with parameter validation.
- Agent constructs validated request body matching schema
- Prompts user for execution confirmation
- Executes tool and confirms response status
Good Fit vs. Poor Fit Criteria for AWS Service Catalog
Architectural guidelines to determine when to adopt this integration and when to explore alternatives.
When to Choose / Good Fit
- AI coding assistants in Claude Desktop or Cursor requiring structured tool access to AWS Service Catalog.
- Developers who want standardized OpenAPI-to-MCP translation without building custom server code.
- Workflows that benefit from automated parameter validation against official OpenAPI 3.0 schemas.
- Teams seeking zero-maintenance hosted JSON configurations for easy distribution.
When to Avoid / Poor Fit
- Ultra-high frequency data ingestion exceeding typical LLM context windows and token rate limits.
- Unattended autonomous agent loops with write access where human approval of mutations is mandatory.
- Environments lacking outbound internet access to upstream AWS Service Catalog API servers.
Verification & Evidence Audit: AWS Service Catalog
OpenAPI 3.0 specification parsed and validated via automated build pipeline.
Independent Evidence Checks
Valid specification version 2015-12-10 with 10 endpoints indexed.
No authentication required.
JSON Schemas mapped to MCP tools/call standard format.
Automated schema validation only; live upstream API calls require developer credentials.
Project Health & Maintenance Audit: AWS Service Catalog
ActiveActivity & Cadence
Transparent Quality Score Breakdown
Alternatives & Comparison Table (Cloud Infrastructure)
Comparative trade-offs between AWS Service Catalog and similar ecosystem tools in the Cloud Infrastructure category.
| Option | Best For | Main Difference vs. AWS Service Catalog | Setup / Runtime | Explore |
|---|---|---|---|---|
| Access Analyzer | Developers needing Cloud Infrastructure operations with 10 tools | 10 endpoints vs 10 endpoints | auto / v2019-11-01 | View → |
| ADHybridHealthService | Developers needing Cloud Infrastructure operations with 10 tools | 10 endpoints vs 10 endpoints | auto / v2014-01-01 | View → |
| AdvisorManagementClient | Developers needing Cloud Infrastructure operations with 9 tools | 9 endpoints vs 10 endpoints | auto / v2016-07-12-preview | View → |
9. Error Resolution & Troubleshooting Guide
Contextual diagnostics for HTTP status codes and JSON-RPC tool bridge operations.
-32600 (Invalid Request)Root Cause: Malformed JSON-RPC payload sent to local MCP bridge process.
Resolution Action: Verify MCP client payload adheres to JSON-RPC 2.0 specification.
-32601 (Method Not Found)Root Cause: Requested operation does not exist in mapped AWS Service Catalog OpenAPI endpoint schemas.
Resolution Action: Inspect Section 5 endpoints table to confirm valid method names and paths.
-32602 (Invalid Params)Root Cause: Missing or invalid parameters for target tool operation.
Resolution Action: Check parameter data types against OpenAPI JSON Schema specification.
429 Rate Limit ExceededRoot Cause: Upstream AWS Service Catalog API request rate limit quota reached.
Resolution Action: Implement exponential backoff in tool execution loop or verify provider plan quotas.
OPENAPI_GATEWAY_TIMEOUTRoot Cause: Upstream AWS Service Catalog endpoint response latency exceeded timeout threshold.
Resolution Action: Verify network connectivity and check provider system status dashboard.
Official Verified Sources for AWS Service Catalog
Authoritative upstream repositories, specifications, package registries, and configuration endpoints.
Official Upstream Documentation
Official developer documentation and API reference for AWS Service Catalog.
https://docs.aws.amazon.com/servicecatalog/OpenAPI 3.0 Specification
Machine-readable OpenAPI schema source used for MCP tool mapping.
https://api.apis.guru/v2/specs/amazonaws.com/servicecatalog/2015-12-10/openapi.jsonHosted MCPBridge Configuration
Pre-generated Model Context Protocol JSON configuration hosted on MCPBridge.
https://mcpbridge.org/config/amazonaws-com-servicecatalog.jsonOpenAPI-to-MCP Converter Tool
Client-side browser converter to customize or filter endpoint tools.
https://mcpbridge.org/convert/Claim & Maintainer Verification
Submit a claim to verify API publisher ownership and update metadata.
https://github.com/stormlive-ai/mcp-bridge-docs/issues/new?title=Claim+Listing%3A+AWS+Service+Catalog+%28api%3A+amazonaws-com-servicecatalog%29&labels=claim-listing&body=%23%23+Claim+Listing+Request%0A%0AI+would+like+to+claim+this+listing%3A%0A%0A-+**Type%3A**+api%0A-+**ID%3A**+amazonaws-com-servicecatalog%0A-+**Name%3A**+AWS+Service+Catalog%0A%0A%23%23%23+Your+Information%0A%0A**GitHub+Handle%3A**+%3C%21--+your+GitHub+username+--%3E%0A%0A**Email%3A**+%3C%21--+optional%2C+for+verification+--%3E%0A%0A**Relationship+to+this+API%3A**%0A-+%5B+%5D+I+am+the+API+provider+%2F+maintainer%0A-+%5B+%5D+I+am+an+authorized+representative%0A-+%5B+%5D+Other%3A%0A%0A%23%23%23+Verification+Method%0A-+%5B+%5D+I+will+add+a+CNAME%2FTXT+record+to+verify+domain+ownership%0A-+%5B+%5D+I+can+confirm+from+an+email+address+at+the+provider+domain%0A-+%5B+%5D+I+maintain+the+GitHub+repository%0A%0A%23%23%23+Updates+I%27d+Like+to+Make+%28optional%29%0A%3C%21--+What+would+you+like+to+update%3F+Description%2C+links%2C+category%2C+etc.+--%3E%0A%0A---%0A*Submitted+via+MCP-Bridge+claim+form*Frequently Asked Technical Questions: AWS Service Catalog
Targeted developer questions regarding installation, client configuration, credentials, and error resolution.
The AWS Service Catalog MCP server connects AI coding assistants (Claude Desktop, Cursor, VS Code, Zed) to the AWS Service Catalog API using the Model Context Protocol. It converts 10 OpenAPI operations into native MCP tools callable during chat sessions.