{"id":98851,"date":"2025-08-21T07:57:23","date_gmt":"2025-08-21T07:57:23","guid":{"rendered":"https:\/\/www.newsbeep.com\/us\/98851\/"},"modified":"2025-08-21T07:57:23","modified_gmt":"2025-08-21T07:57:23","slug":"enhance-ai-agents-using-predictive-ml-models-with-amazon-sagemaker-ai-and-model-context-protocol-mcp","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/us\/98851\/","title":{"rendered":"Enhance AI agents using predictive ML models with Amazon SageMaker AI and Model Context Protocol (MCP)"},"content":{"rendered":"\n

Machine learning<\/a> (ML) has evolved from an experimental phase to becoming an integral part of business operations. Organizations now actively deploy ML models for precise sales forecasting, customer segmentation, and churn prediction. While traditional ML continues to transform business processes, generative AI<\/a> has emerged as a revolutionary force, introducing powerful and accessible tools that reshape customer experiences.<\/p>\n

Despite generative AI\u2019s prominence, traditional ML solutions remain essential for specific predictive tasks. Sales forecasting, which depends on historical data and trend analysis, is most effectively handled by established ML algorithms including random forests, gradient boosting machines (like XGBoost), autoregressive integrated moving average (ARIMA) models, long short-term memory (LSTM) networks, and linear regression techniques. Traditional ML models, such as K-means and hierarchical clustering, also excel in customer segmentation and churn prediction applications. Although generative AI demonstrates exceptional capabilities in creative tasks such as content generation, product design, and personalized customer interactions, traditional ML models maintain their superiority in data-driven predictions. Organizations can achieve optimal results by using both approaches together, creating solutions that deliver accurate predictions while maintaining cost efficiency.<\/p>\n

To achieve this, we showcase in this post how customers can expand AI agents\u2019 capabilities by integrating predictive ML models and Model Context Protocol (MCP)<\/a>\u2014an open protocol that standardizes how applications provide context to large language models<\/a> (LLMs)\u2014on Amazon SageMaker AI<\/a>. We demonstrate a comprehensive workflow that enables AI agents to make data-driven business decisions by using ML models hosted SageMaker. Through the use of Strands Agents SDK<\/a>\u2014an open source SDK that takes a model-driven approach to building and running AI agents in only a few lines of code\u2014and flexible integration options, including direct endpoint access and MCP, we show you how to build intelligent, scalable AI applications that combine the power of conversational AI with predictive analytics.<\/p>\n

Solution overview <\/p>\n

This solution enhances AI agents by having ML models deployed on Amazon SageMaker AI endpoints integrate with AI Agents, to enable them to make data-driven business decisions through ML predictions. An AI agent is an LLM-powered application that uses an LLM as its core \u201cbrain\u201d to autonomously observe its environment, plan actions, and execute tasks with minimal human input. It integrates reasoning, memory, and tool use to perform complex, multistep problem-solving by dynamically creating and revising plans, interacting with external systems, and learning from past interactions to optimize outcomes over time. This enables AI agents to go beyond simple text generation, acting as independent entities capable of decision-making and goal-directed actions in diverse real-world and enterprise scenarios.For this solution, the AI agent is developed using the Strands Agents SDK, which allows for rapid development from simple assistants to complex workflows. Predictive ML models are hosted on Amazon SageMaker AI and will be used as tools by the AI agent. This can happen in two ways: agents can directly invoke SageMaker endpoints for more direct access to model inference capabilities or use the MCP protocol to facilitate the interaction between AI agents and the ML models. Both options are valid: direct tool invocation doesn\u2019t require additional infrastructure by embedding the tool calling directly in the agent code itself, whereas MCP enables dynamic discovery of the tools and decoupling of agent and tool execution through the introduction of an additional architectural component, the MCP server itself. For scalable and secure implementation of the tool calling logic, we recommend the MCP approach. Although we\u2019re recommending MCP, we discuss and implement the direct endpoint access as well, to give readers the freedom to choose the approach that they prefer.<\/p>\n

Amazon SageMaker AI offers two methods to host multiple models behind a single endpoint: inference components and multi-model endpoints. This consolidated hosting approach enables efficient deployment of multiple models in one environment, which optimizes computing resources and minimizes response times for model predictions. For demonstration purposes, this post deploys only one model on one endpoint. If you want to learn more about inference components, refer to the Amazon SageMaker AI documentation Shared resource utilization with multiple models<\/a>. To learn more about multi-model endpoints, refer to the Amazon SageMaker AI documentation Multi-model endpoints<\/a>.<\/p>\n

Architecture <\/p>\n

In this post, we define a workflow for empowering AI agents to make data-driven business decisions by invoking predictive ML models using Amazon SageMaker AI. The process begins with a user interacting through an interface, such as a chat-based assistant or application. This input is managed by an AI agent developed using the open source Strands Agents SDK. Strands Agents adopts a model-driven approach, which means developers define agents with only a prompt and a list of tools, facilitating rapid development from simple assistants to complex autonomous workflows.<\/p>\n

When the agent is prompted with a request that requires a prediction (for example, \u201cwhat will be the sales for H2 2025?\u201d), the LLM powering the agent decided to interact with the Amazon SageMaker AI endpoint hosting the ML model. This can happen in two ways: directly using the endpoint as a custom tool of the Strands Agents Python SDK or by calling the tool through MCP. With MCP, the client application can discover the tools exposed by the MCP server, obtain the list of required parameters, and format the request to the Amazon SageMaker inference endpoint. Alternatively, agents can directly invoke SageMaker endpoints using tool annotations (such as @tool), bypassing the MCP server for more direct access to model inference capabilities.<\/p>\n

Finally, the prediction generated by the SageMaker hosted model is routed back through the agent and ultimately delivered to the user interface, enabling real-time, intelligent responses.<\/p>\n

The following diagram illustrates this process. The complete code for this solution is available on GitHub<\/a>.<\/p>\n

\"A<\/p>\n

Prerequisites <\/p>\n

To get started with this solution, make sure you have:<\/p>\n

Solution implementation <\/p>\n

In this solution, we implement a complete workflow that demonstrates how to use ML models deployed on Amazon SageMaker AI as specialized tools for AI agents. This approach enables agents to access and use ML capabilities for enhanced decision-making without requiring deep ML expertise. We play the role of a data scientist tasked with building an agent that can predict demand for one product. To achieve this, we train a time-series forecasting model, deploy it, and expose it to an AI agent.<\/p>\n

The first phase involves training a model using Amazon SageMaker AI. This begins with preparing training data by generating synthetic time series data that incorporates trend, seasonality, and noise components to simulate realistic demand patterns. Following data preparation, feature engineering is performed to extract relevant features from the time series data, including temporal features such as day of week, month, and quarter to effectively capture seasonality patterns. In our example, we train an XGBoost model using the XGBoost container available as 1P container in Amazon SageMaker AI to create a regression model capable of predicting future demand values based on historical patterns. Although we use XGBoost for this example because it\u2019s a well-known model used in many use cases, you can use your preferred container and model, according to the problem you\u2019re trying to solve. For the sake of this post, we won\u2019t detail an end-to-end example of training a model using XGBoost. To learn more about this, we suggest checking out the documentation Use XGBoost with the SageMaker Python SDK<\/a>. Use the following code:<\/p>\n

from\u00a0sagemaker.xgboost.estimator import\u00a0XGBoost<\/p>\n

xgb_estimator = XGBoost(…)
\nxgb_estimator.fit({‘train’: train_s3_path, ‘validation’: val_s3_path}) <\/p>\n

Then, the trained model is packaged and deployed to a SageMaker AI endpoint, making it accessible for real-time inference through API calls:<\/p>\n

predictor = xgb_estimator.deploy(
\n \u00a0 \u00a0initial_instance_count=1,
\n \u00a0 \u00a0instance_type=instance_type,
\n \u00a0 \u00a0serializer=JSONSerializer(),
\n \u00a0 \u00a0deserializer=JSONDeserializer()
\n) <\/p>\n

After the model is deployed and ready for inferences, you need to learn how to invoke the endpoint. To invoke the endpoint, write a function like this:<\/p>\n

ENDPOINT_NAME = “serverless-xgboost”
\nREGION = boto3.session.Session().region_name<\/p>\n

def invoke_endpoint(payload: list):
\n\u00a0\u00a0 \u00a0“””
\n\u00a0\u00a0 \u00a0 \u00a0 \u00a0Use the model deployed on the Amazon SageMaker AI endpoint to generate predictions.
\n\u00a0\u00a0 \u00a0 \u00a0 \u00a0Args:
\n\u00a0\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0payload: a list of lists containing the inputs to generate predictions from
\n\u00a0\u00a0 \u00a0 \u00a0 \u00a0Returns:
\n\u00a0\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0predictions: an NumPy array of predictions
\n\u00a0\u00a0 \u00a0“””
\n\u00a0\u00a0 \u00a0sagemaker_runtime = boto3.client(“sagemaker-runtime”, region_name=REGION)
\n\u00a0\u00a0 \u00a0response = sagemaker_runtime.invoke_endpoint(
\n\u00a0\u00a0 \u00a0 \u00a0 \u00a0EndpointName=ENDPOINT_NAME,
\n\u00a0\u00a0 \u00a0 \u00a0 \u00a0Body=json.dumps(payload),
\n\u00a0\u00a0 \u00a0 \u00a0 \u00a0ContentType=”application\/json”,
\n\u00a0\u00a0 \u00a0 \u00a0 \u00a0Accept=”application\/json”
\n\u00a0\u00a0 \u00a0)
\n\u00a0\u00a0 \u00a0predictions = json.loads(response[‘Body’].read().decode(“utf-8”))
\n\u00a0\u00a0 \u00a0return np.array(predictions) <\/p>\n

Note that the function invoke_endpoint() has been written with proper docstring. This is key to making sure that it can be used as a tool by LLMs because the description is what allows them to choose the right tool for the right task. YOu can turn this function into a Strands Agents tool thanks to the @tool decorator:<\/p>\n

from\u00a0strands import\u00a0tool<\/p>\n

@tool()
\ndef\u00a0invoke_endpoint(payload: list):
\n\u00a0 \u00a0 …. <\/p>\n

And to use it, pass it to a Strands agent:<\/p>\n

As you run this code, you can confirm the output from the agent, which correctly identifies the need to call the tool and executes the function calling loop:<\/p>\n

To fulfill the User’s request, I need to invoke the Amazon SageMaker
\nendpoint with the provided input data. The input is a list of lists, which is the
\nrequired format for the ‘generate_prediction_with_sagemaker’ tool. I will use this
\ntool to get the predictions. <\/p>\n

Tool #1: generate_prediction_with_sagemaker The predictions from the Amazon SageMaker
\nendpoint are as follows:
\n“`json {\u00a0 “predictions”: [89.8525238, 52.51485062, 58.35247421, 62.79786301, 85.51475525] } “` <\/p>\n

As the agent receives the prediction result from the endpoint tool, it can then use this as an input for other processes. For example, the agent could write the code to create a plot based on these predictions and show it to the user in the conversational UX. It could send these values directly to business intelligence (BI) tools such as Amazon QuickSight<\/a> or Tableau<\/a> and automatically update enterprise resource planning (ERP) or customer relationship management (CRM) tools such as SAP<\/a> or Salesforce<\/a>.<\/p>\n

Connecting to the endpoint through MCP <\/p>\n

You can further evolve this pattern by having an MCP server invoke the endpoint rather than the agent itself. This allows for the decoupling of agent and tool logic and an improved security pattern because the MCP server will be the one with the permission to invoke the endpoint. To achieve this, implement an MCP server using the FastMCP<\/a> framework that wraps the SageMaker endpoint and exposes it as a tool with a well-defined interface. A tool schema must be specified that clearly defines the input parameters and return values for the tool, facilitating straightforward understanding and usage by AI agents. Writing the proper docstring when defining the function achieves this. Additionally, the server must be configured to handle authentication securely, allowing it to access the SageMaker endpoint using AWS credentials or AWS roles. In this example, we run the server on the same compute as the agent and use stdio as communication protocol. For production workloads, we recommend running the MCP server on its own AWS compute and using transport protocols based on HTTPS (for example, Streamable HTTP). If you want to learn how to deploy MCP servers in a serverless fashion, refer to this official AWS GitHub repository<\/a>. Here\u2019s an example MCP server:<\/p>\n

from\u00a0mcp.server.fastmcp import\u00a0FastMCP<\/p>\n

mcp =\u00a0FastMCP(“SageMaker App”)
\nENDPOINT_NAME =\u00a0os.environ[“SAGEMAKER_ENDPOINT_NAME”]<\/p>\n

@mcp.tool()
\nasync\u00a0def\u00a0invoke_endpoint(payload: list):
\n\u00a0\u00a0 \u00a0“””\u00a0Use the model … “””
\n\u00a0 \u00a0 […]
\n\u00a0\u00a0\u00a0\u00a0
\nif\u00a0__name__\u00a0==\u00a0“__main__”:
\n\u00a0\u00a0 \u00a0mcp.run(=”stdio”) <\/p>\n

Finally, integrate the ML model with the agent framework. This begins with setting up Strands Agents to establish communication with the MCP server and incorporate the ML model as a tool. A comprehensive workflow must be created to determine when and how the agent should use the ML model to enhance its capabilities. The implementation includes programming decision logic that enables the agent to make informed decisions based on the predictions received from the ML model. The phase concludes with testing and evaluation, where the end-to-end workflow is validated by having the agent generate predictions for test scenarios and take appropriate actions based on those predictions.<\/p>\n

Clean up <\/p>\n

When you\u2019re done experimenting with the Strands Agents Python SDK and models on Amazon SageMaker AI, you can delete the endpoint you\u2019ve created to stop incurring unwanted charges. To do that, you can use either the AWS Management Console<\/a>, the SageMaker Python SDK<\/a>, or the AWS SDK for Python (boto3)<\/a>:<\/p>\n

# SageMaker Python SDK
\npredictor.delete_model()
\npredictor.delete_endpoint()<\/p>\n

# Alternatively, boto3
\nsagemaker_runtime.delete_endpoint(EndpointName=endpoint_name) <\/p>\n

Conclusion <\/p>\n

In this post, we demonstrated how to enhance AI agents\u2019 capabilities by integrating predictive ML models using Amazon SageMaker AI and the MCP. By using the open source Strands Agents SDK and the flexible deployment options of SageMaker AI, developers can create sophisticated AI applications that combine conversational AI with powerful predictive analytics capabilities. The solution we presented offers two integration paths: direct endpoint access through tool annotations and MCP-based integration, giving developers the flexibility to choose the most suitable approach for their specific use cases. Whether you\u2019re building customer service chat assistants that need predictive capabilities or developing complex autonomous workflows, this architecture provides a secure, scalable, and modular foundation for your AI applications. As organizations continue to seek ways to make their AI agents more intelligent and data-driven, the combination of Amazon SageMaker AI, MCP, and the Strands Agents SDK offers a powerful solution for building the next generation of AI-powered applications.<\/p>\n

For readers unfamiliar with connecting MCP servers to workloads running on Amazon SageMaker AI, we suggest Extend large language models powered by Amazon SageMaker AI using Model Context Protocol<\/a> in the AWS Artificial Intelligence Blog, which details the flow and the steps required to build agentic AI solutions with Amazon SageMaker AI.<\/p>\n

To learn more about AWS commitment to the MCP standard, we recommend reading Open Protocols for Agent Interoperability Part 1: Inter-Agent Communication on MCP<\/a> in the AWS Open Source Blog, where we announced that AWS is joining the steering committee for MCP to make sure developers can build breakthrough agentic applications without being tied to one standard. To learn more about how to use MCP with other technologies from AWS, such as Amazon Bedrock Agents<\/a>, we recommend reading Harness the power of MCP servers with Amazon Bedrock Agents<\/a> in the AWS Artificial Intelligence Blog. Finally, a great way to securely deploy and scale MCP servers on AWS is provided in the AWS Solutions Library at Guidance for Deploying Model Context Protocol Servers on AWS<\/a>.<\/p>\n

About the authors <\/p>\n

\"\"Saptarshi Banerjee serves as a Senior Solutions Architect at AWS, collaborating closely with AWS Partners to design and architect mission-critical solutions. With a specialization in generative AI, AI\/ML, serverless architecture, Next-Gen Developer Experience tools and cloud-based solutions, Saptarshi is dedicated to enhancing performance, innovation, scalability, and cost-efficiency for AWS Partners within the cloud ecosystem.<\/p>\n

\"\"Davide Gallitelli is a Senior Worldwide Specialist Solutions Architect for Generative AI at AWS, where he empowers global enterprises to harness the transformative power of AI. Based in Europe but with a worldwide scope, Davide partners with organizations across industries to architect custom AI agents that solve complex business challenges using AWS ML stack. He is particularly passionate about democratizing AI technologies and enabling teams to build practical, scalable solutions that drive organizational transformation.<\/p>\n","protected":false},"excerpt":{"rendered":"Machine learning (ML) has evolved from an experimental phase to becoming an integral part of business operations. Organizations…\n","protected":false},"author":2,"featured_media":98852,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[182,181,507,74],"class_list":["post-98851","post","type-post","status-publish","format-standard","has-post-thumbnail","category-artificial-intelligence","tag-ai","tag-artificial-intelligence","tag-artificialintelligence","tag-technology"],"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/posts\/98851","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/comments?post=98851"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/posts\/98851\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/media\/98852"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/media?parent=98851"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/categories?post=98851"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/tags?post=98851"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}