Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Build the engagement layer once: one Microsoft Foundry agent in Teams acts across Salesforce, ServiceNow and your other systems of record, always as the signed-in user. Open-source reference implementation (APIM identity propagation, MCP meta-tools, azd).
Customer 360 Assistant is an open-source reference implementation built on Microsoft Teams, Microsoft Foundry and Azure API Management. People ask in Teams. One Foundry agent routes each request to the right tool. In this sample that means Salesforce and ServiceNow; Jira, SAP, Workday or your own APIs follow the same pattern. Every action runs as the signed-in user, with their own permissions in each system.
Alice, an account manager, has five minutes before a call with Contoso. In a Teams group chat she gets a 360° view across Salesforce and ServiceNow. After the call, she updates the CRM in one sentence. Every action runs as Alice.
Animated mock-ups with demo data (Contoso, Alice, Bob). Source and render instructions: video/. Consent is designed to happen once per system; a current Foundry platform issue can ask users to consent again after about an hour (known issue).
The thread through every layer is the user's identity. People sign in once with Microsoft Entra ID, and every tool call carries that identity.
azd deploy the stack once the prerequisites are in place.Adapted from docs/TEST_PROMPTS_360.md, which run against seeded demo data. Every prompt runs with the asker's own access; the last one is the CRM update shown in the video.
No shared credential touches business data. A minimal-access service account only maps Alice to her Salesforce user. Identity propagation stops privilege escalation, but it cannot stop an agent from misreading intent, so keep confirmations for destructive actions (what it does not protect against).
Salesforce and ServiceNow are working examples. Every system follows the same three-part pattern:
Jira, SAP, Workday and your own APIs are not included in this repository; they are where the pattern goes next.
Why meta-tools instead of one tool per object? Many MCP servers define one tool per object, so every new object means new code and a longer tool list. A meta-tool server works like a shell: the agent discovers objects, learns their fields and builds the query itself, with the user's own access. The tool list stays the same whatever the size of the org. See the meta-tool pattern.
In this repository
whoami, list_objects, describe_object, soql_query, search_records, write_record, process_approval) on Azure Container Apps.salesforce-assistant and customer360-assistant, wired through OAuth2 identity-passthrough connections. Their behaviour comes from six versioned Foundry skills (salesforce-crm, servicenow-itsm, customer360-correlation, revenue-at-risk, meeting-prep, change-risk), with a lean system prompt on top.azd, Salesforce org setup scripts, demo-data seeding and E2E tests.The two-repo Customer 360 demo adds snow-meta-tool (ServiceNow tools, same pattern) and correlated demo data (setup).
[!NOTE] This is a reference implementation with demo data, not an audited production product. Read the current scope and limitations and the known platform issues before you adapt it.
The rest of this page is the technical path: architecture, identity flow, tools and deployment.
The user asks a question. The agent discovers objects, learns schemas, and queries Salesforce — all through the same seven tools, all with the user's own identity.
APIM handles a three-phase exchange: validate the Azure AD JWT, resolve the Salesforce username, and acquire a per-user Salesforce token. The MCP server never sees Azure AD credentials. Foundry obtains the user's delegated token through an OAuth2 identity-passthrough connection against a customer-owned Entra app (one-time consent per user) — Agent Service no longer forwards Microsoft-audience tokens to custom MCP endpoints.
Deep dive: Detailed OBO exchange animation | Full detail PNG | Excalidraw source
v2 (2026-07): OAuth2 identity passthrough. Foundry Agent Service blocks Microsoft-audience tokens to custom MCP endpoints (
Cannot pass Microsoft token to untrusted MCP endpoint), which ended the originalUserEntraTokenconnection. v2 uses an OAuth2 identity-passthrough connection backed by your own Entra app: one-time consent per user, same three-phase OBO exchange. Rationale and migration: CHANGELOG.md.
The seven tool definitions come to roughly 1.65K tokens per model call (about 2.1K with the server instructions), whatever the size of the org. Measured from the server's tools/list with the o200k_base tokenizer (October 2026); details in docs/deepdive.md. Field schemas are loaded on demand through describe_object rather than pre-loaded into the system prompt.
skills/<name>/SKILL.md becomes a Foundry skill version. azd up uploads a new version only when the content changes, and the agents pin exact versions. Prompt agents can't load skills at runtime yet, so the hook compiles the pinned versions into the instructions (SKILLS_MODE=inline). SKILLS_MODE=native is ready for when the GitHub Copilot harness is available. See AGENT.md.azd env set C360_TOOLS_MODE toolbox serves Customer 360 from a single Foundry Toolbox that holds both MCP servers and all skills.python hooks/postprovision.py --rollback restores the previous version.python scripts/test_e2e_customer360.py [--path version|app] runs one or more turns per skill plus a write guard.For detailed technical explanations, see docs/deepdive.md:
New to this project? Follow the step-by-step installation guide for a complete walkthrough from a clean Azure subscription and Salesforce org.
You need an Azure subscription (Contributor + User Access Administrator), a Salesforce Developer or Sandbox org, and the Azure Developer CLI, Azure CLI, Python 3.11+, Docker Desktop, the Salesforce CLI and OpenSSL. Versions and links are in Phase 0 of the installation guide.
If you already have a configured Salesforce org and certificate:
git clone https://github.com/ozgurkarahan/salesforce-meta-tool-identity-propagation.git
cd salesforce-meta-tool-identity-propagation
pip install -r requirements.txt
azd env new obo
azd env set SF_INSTANCE_URL "https://your-org.my.salesforce.com"
azd env set SF_CONNECTED_APP_CLIENT_ID "<connected-app-consumer-key>"
azd env set SF_SERVICE_ACCOUNT_USERNAME "<[email protected]>"
# v2: Entra app backing the OAuth2 identity-passthrough connection
# (create it first -- see docs/installation.md Phase 3)
azd env set MCP_OAUTH_CLIENT_ID "<mcp-oauth-app-id>"
azd env set MCP_OAUTH_CLIENT_SECRET "<mcp-oauth-app-secret>"
azd up
The postprovision hook automatically uploads certs/sf-jwt-bearer.pfx to Key Vault, creates the APIM certificate binding, and sets SF_JWT_BEARER_CERT_THUMBPRINT. No manual thumbprint step needed.
After azd up completes, open the Chat App URL printed at the end. Sign in with your Azure AD account and send a message (e.g., "Show me my Salesforce accounts").
azd env set SF_INSTANCE_URL "https://your-org.my.salesforce.com"
azd env set SF_CONNECTED_APP_CLIENT_ID "<consumer-key>"
azd env set SF_SERVICE_ACCOUNT_USERNAME "<[email protected]>"
azd env set MCP_OAUTH_CLIENT_ID "<mcp-oauth-app-id>" # v2 -- see installation guide Phase 3
azd env set MCP_OAUTH_CLIENT_SECRET "<mcp-oauth-app-secret>"
azd upThe full table moved to the installation guide: Reference: Environment Variables.
The annotated tree moved to the installation guide: Reference: Project Structure.
Troubleshooting moved to the installation guide: Common Issues. That section also covers the v2 consent and token-expiry issues.
This repository is part of the Identity Propagation series on end-to-end user identity for AI agents: no shared service account reading or writing business data, and every action traceable to a real user. Read the story: From Theory to Production: Salesforce Meta-Tool & Identity Propagation.
Contributions are welcome. Please open an issue or submit a pull request.
This project uses azd for deployment. See Deployment and Setup to get a local environment running.
Related article: The Meta-Tool Pattern Applied to Enterprise on LinkedIn.
Build the engagement layer once: one Microsoft Foundry agent in Teams acts across Salesforce, ServiceNow and your other systems of record, always as the signed-in user. Open-source reference implement
ภาพรวม
Build the engagement layer once: one Microsoft Foundry agent in Teams acts across Salesforce, ServiceNow and your other systems of record, always as the signed-in user. Open-source reference implementation (APIM identity propagation, MCP meta-tools, azd).
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Salesforce Meta Tool Identity Propagation ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 Build the engagement layer once: one Microsoft Foundry agent in Teams acts across Salesforce, ServiceNow and your other systems of record, always as the signed-in user. Open-source reference implementation (APIM identity propagation, MCP meta-tools, azd).