← Explore all mcp servers

CLOUD OPERATIONS / AWS Labs

SageMaker Unified Studio Spark Upgrade MCP

Remote EMR Spark upgrade endpoint reached by a local stdio proxy that assumes an IAM role, then edits code and submits validation jobs.

“Remote stdio-proxied server that plans EMR Spark upgrades, then applies code edits and submits validation jobs.”

01 / THE REASONING

Why this made the selection.

  • The AWS Authentication section assumes an IAM role into spark-upgrade-profile, and the stdio proxy is started with that profile.
  • After planning, the code-edit tool applies source updates and validation submits remote EMR jobs that can store artifacts on an S3 path the user names.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • src/sagemaker-unified-studio-spark-upgrade-mcp-server/README.md
  • README.md
  • LICENSE

Our findings

  • The AWS Authentication section writes profile spark-upgrade-profile with an assumed IAM role, a source profile, and a region. The stdio proxy is then pointed at that profile and the spark-upgrade URL.
  • The documented flow plans the upgrade, updates dependencies and compiles, applies code edits for Spark incompatibilities, then submits remote EMR validation jobs. A saved plan JSON can be reused, and specific transformations can be excluded.
  • Supported paths are Spark 2.4 through 3.5. EMR on EC2 sources start at 5.20.0 and targets stop at 7.12.0 and must be newer than 5.20.0. EMR Serverless sources start at 6.6.0 and targets stop at 7.12.0.
  • The README says the caller keeps full control of changes. It does not name a dry-run mode separate from the plan step and that control.

Not established by this review

  • The resource was not executed.
  • The server was not started and no tool was called.
  • No EMR validation job was submitted and no project files were edited.
  • The linked AWS docs and the docusaurus copy of this page were not fetched.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Run the three unindented aws configure set lines that point profile spark-upgrade-profile at an IAM role, a source profile, and a region.
  2. Register a stdio client whose command is uvx and whose first argument is the indented mcp-proxy-for-aws@latest line, aimed at the spark-upgrade URL.
  3. Kiro, Cline, and GitHub Copilot are named as clients. Their extra setup is linked out of this file and was not opened.

Before you start

  • uv
  • AWS CLI profile spark-upgrade-profile assuming an IAM role
  • A local stdio MCP client

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Spark upgrade README ↗Checked

    https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/sagemaker-unified-studio-spark-upgrade-mcp-server/README.md

    Supports: Role assumption, code edits, and remote EMR validation

  2. Repository licence ↗Checked

    https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE

    Supports: Apache License Version 2.0 header

  3. https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/README.md

    Supports: States the project licence is Apache-2.0

Evidence & Ask