I'm trying to figure out how to effectively integrate AWS AgentCore with a fully managed remote MCP server provided by a SaaS platform, like Salesforce or Monday. My goal is to have my AgentCore agent connect directly to these MCP servers without the need to run my own server or deploy a container. Specifically, I'm looking for a setup where:
- AgentCore can talk directly to a SaaS-hosted MCP endpoint.
- Authentication is handled through OAuth, API keys, or the SaaS platform's authentication methods.
- There is no requirement for customer-managed compute.
I'm curious about a few things:
1. Does AgentCore support remote MCP endpoints like HTTP, SSE, or WebSocket out of the box?
2. Is there a recognized method for integrating with SaaS-managed MCP servers?
3. Are there any limitations that necessitate running MCP within customer-managed environments?
4. Has anyone managed to connect AgentCore to a third-party MCP server without using containers? I'd appreciate any insights, documentation, or real-world examples!
4 Answers
I've been using fastMCP on a lambda function and managed to avoid hosting my own MCP server just fine. You can definitely add an existing MCP as a target in AgentCore Gateway without needing to set up anything on your end. Should work well for what you need!
It sounds like AgentCore might not be the best fit for your needs. AgentCore mainly provides the runtime for running agents, while the actual consumption of the MCP server happens in the agent's code. You might want to check out frameworks like LangGraph, CrewAI, or Strands for coding that connection. For instance, Strands has a useful guide on integrating with MCP servers directly, which might be what you're looking for. Although you can connect to the MCP via the AgentCore Gateway by designating it as a target, it could be a bit over-complicated for your requirements.
Also, remember that AgentCore Gateway is designed to transform existing APIs and Lambda functions, making it easier to integrate with third-party tools. It could really streamline things for you.
Just to clarify, AgentCore offers a suite of services. If you aim to run agent code with an SDK like Strands Agents, containerization is typically necessary for the AgentCore Runtime. But, you could also run these agents in Lambda, especially with the newer durable functions. Regardless of where your agent runs, you can authenticate and connect to a remote MCP using the SDK directly. If you're managing multiple agents and want them to connect to various MCPs, AgentCore Gateway might be helpful to abstract authentication and improve monitoring.
Simple solution: List the MCP as a Lambda function. This approach could simplify things and eliminate the need for additional complexity in your setup.
Totally agree! It's always good to consider the overall architecture rather than just jumping into a solution. Plus, those frameworks do offer a ton of resources to help guide the integration process.