awslabs / awslabs/agentcore-samples

Add Salesforce + AWS for SAP MCP Server integration tutorial (filling "Coming soon" gap)

Open
#1,456 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
3.4k
Forks
1.3k
Avg merge
1d 22h
Merged PRs (30d)
30

Description

## Summary

The README at `05-mcp-server-as-a-target/03-authorization-code-flow/` lists Salesforce as "Coming soon" alongside Snowflake and Atlassian. Only the GitHub example exists today. I want to contribute a multi-ISV orchestration tutorial that shows how to connect AWS for SAP MCP Server and Salesforce to a single AgentCore Gateway — and query both from one agent.

## Why this matters

Enterprises run business-critical data across multiple SaaS platforms — SAP for ERP, Salesforce for CRM, Workday for HCM. Today, no sample shows how to connect multiple ISV systems to one AgentCore Gateway and orchestrate cross-system queries from a single agent. Customers ask: "How do I build an agent that reads my SAP inventory AND my Salesforce pipeline in one conversation?"

This tutorial answers that question with a working, reproducible example.

## What it covers

1. **Salesforce as a Gateway integration target** — OAuth2 Connected App setup, CustomOauth2 provider configuration, CRUD operations across Accounts, Opportunities, Leads, and Campaigns
2. **AWS for SAP MCP Server as a Gateway MCP target** — deploying the SAP MCP Server on AgentCore Runtime, adding it as a gateway target, querying OData services
3. **Example queries** — cross-system prompts customers can run immediately: customer 360 (combine SAP business partner data with Salesforce account history), pipeline-to-inventory reconciliation, lead-to-order tracking across systems

## Proposed files

```
01-tutorials/02-AgentCore-gateway/11-multi-isv-orchestration/
├── 01-salesforce-gateway-target.ipynb # Salesforce as integration target
├── 02-sap-mcp-server-target.ipynb # AWS for SAP MCP Server as MCP target
├── 03-cross-isv-queries.ipynb # Cross-system example queries
└── README.md
```

The `03-authorization-code-flow/` README can link to `01-salesforce-gateway-target.ipynb` to resolve the Salesforce "Coming soon" placeholder.

## References

- [AWS for SAP MCP Server — What's New](https://aws.amazon.com/about-aws/whats-new/2026/05/aws-sap-mcp-amazon-bedrock/)
- [AWS for SAP MCP Server — Docs](https://docs.aws.amazon.com/mcp-sap/latest/awsforsapmcp/introduction.html)
- [Salesforce Gateway integration — Docs](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-integrations.html#gateway-target-integrations-supported-apis-salesforce)

## PCSR

Will complete the Public Content Security Review before submitting the PR.

Contributor guide

Open the contributing guide

Research direction

Start with the README at 05-mcp-server-as-a-target/03-authorization-code-flow/ and the Salesforce and AWS for SAP MCP Server documentation. Review the proposed notebooks in 01-tutorials/02-AgentCore-gateway/11-multi-isv-orchestration/ and define a reproducible flow covering both targets and cross-system queries. Done means the three notebooks and README work together, and the authorization-code-flow README links to the Salesforce tutorial.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
api, cloud, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.