Curated, customer-specific MCP servers that give AI agents, people and developers governed access to the SAP processes and data relevant to their work, live and in real time, on any surface and in any IDE, with nothing installed inside SAP.
Vigience MCP exposes the SAP, Salesforce and other systems of record processes and data that are relevant to your use cases, as clear, concise tools an agent can use well. It runs on Vigience Overcast, the platform that has done this for Salesforce customers for more than ten years.
Most of what a customer needs already exists: more than 200 prebuilt, pre-integrated components cover 80 percent or more of typical requirements, from customer master data to orders, quotes, deliveries and assets. What is missing is configured with the Overcast Component Builder, without code, against SAP’s public APIs. Vigience maintains every component through SAP and Salesforce releases, for all customers at once.
Vigience MCP comes in three editions, each tailored to the customer’s needs, from the MCP servers themselves to the surrounding layers.
Runs inside your Salesforce org
For enterprises running Salesforce that want the MCP server inside their org alongside Agentforce.
Runs on your MuleSoft platform
For enterprises running MuleSoft that want to build their own bespoke MCP server using Vigience accelerators, SAP APIs, skills and more.
Runs without Salesforce CRM
For SAP-only environments without Salesforce. Connects to various backends, including SAP and non-SAP, as well as SAP BTP and MuleSoft.
Real-time data from SAP running wherever your people work, audited all the way through.
By default, agents can only read data from their own platform. SAP remains unreachable, so they cannot reserve parts, create orders, or issue invoices.
Vigience MCP exposes safe SAP operations so agents can execute transactions (order creation, parts issuance, time logging, billing) directly from Agentforce, Claude, ChatGPT, Copilot, or Slack.
Quotes and decisions lack SAP pricing, ATP checks, warranty, and credit status. Agents guess, and errors must be corrected manually.
Agents check live SAP business rules and data first, then act. Pricing, contracts, and credit limits are validated directly in-flow.
SAP exposes tens of thousands of APIs and tables. A generic MCP server overwhelms the LLM, leading to hallucinations and wrong actions.
Each Vigience MCP server is tailored in days to your specific SAP customizing (e.g., exactly the 50 relevant operations with 20 fields).
Bespoke scripts run outside enterprise policy without approval workflows and audit trails.
Vigience MCP enforces permissions, approvals, and rollbacks. No commit reaches SAP without authorization; every step remains traceable.
Nightly syncs and handoffs slow processes down; errors surface hours later.
In-line validation against SAP rules within the interaction; immediate feedback or routed exceptions.
With Vigience MCP, your users and agents can analyze and act on SAP data wherever they work. Design-time tools provide prebuilt SAP integrations and allow creating new ones with point-and-click ease. The MCP server can run on Salesforce, MuleSoft, or standalone. Nothing is installed inside SAP: it works across SAP ECC, SAP S/4HANA Private Cloud Edition, and SAP S/4HANA Public Cloud while keeping the core clean. Beyond SAP, the MCP server can also connect to other third-party backends including Salesforce, Oracle, and Microsoft.
Practical Information About Vigience MCP
What is Vigience MCP?
A curated, customer-specific Model Context Protocol server that gives AI agents, people, and developers governed, real-time read and write access to relevant SAP processes and data, with nothing installed inside SAP.
Why connect AI agents to SAP?
Without connection, agents are limited to their host platform’s data. Connected to SAP, they can autonomously resolve returns, orders, parts requests, warranty claims, and invoices.
How is this different from a generic SAP MCP server?
A generic server dumps the entire API catalog on the LLM, causing confusion and hallucinations. Vigience MCP curates only the required operations, brings multiple SAP systems together, and adds essential governance (authorizations, pre-commit confirmations, audit trails).
How is this different from standard Salesforce-to-SAP integration?
Traditional integrations sync records between systems. Vigience MCP enables agents and humans to run, update, and complete real-time SAP transactions in-flow to resolve cases with AI.
Which SAP systems are supported?
SAP S/4HANA (Public & Private Cloud), SAP ECC, and SAP Business One via BAPIs, RFCs, and OData APIs.
Is Salesforce required?
No. The standalone edition runs completely without Salesforce.
Which AI clients are supported?
Any MCP-compliant client, including Claude, ChatGPT, Copilot, Agentforce, Slack, and IDEs such as Cursor, Claude Code, and Codex.
Does it work with S/4HANA Public Cloud?
Yes. Because nothing is installed inside SAP and access runs through SAP’s public APIs, the same server works on SAP ECC, SAP S/4HANA Private Cloud edition, and SAP S/4HANA Public Cloud.
Can an agent post to SAP without human involvement?
Only when pre-approved by policy. By default, a named human confirms each transaction. For automated workflows, you set policies once and the platform applies them on every run, always maintaining a full audit trail.
Can I audit what the agent does in SAP?
Ja / Yes. Every SAP action executed through Vigience MCP is logged and attributable to the responsible human or agent: what was suggested, what was verified, who confirmed it, and what was committed.
Does it support AI security and compliance?
Yes. Agents operate strictly within the boundaries and authorizations of your SAP and Salesforce security model and the individual user’s permissions. Admins define policies, and the platform enforces them.
How long does implementation take?
A curated MCP server for a first workflow is configured in days, and most customers go live with a full use case in weeks rather than months. The implementation process is standardized and metadata-driven.
What is the pricing model?
Billed per user per month (starting from $10/user/month).
Do I need to replace my existing SAP middleware?
No. Vigience MCP runs with or without middleware. It works alongside your existing tools and can run on MuleSoft if that is your enterprise integration platform.
Can we start small and expand later?
Yes. Many customers begin with a single workflow, like warranty verification or order status checks, and expand progressively to full automation.
How do I get started?
Vigience MCP is available in an early-access program for selected customers. Contact Vigience for a demo, watch the overview video, or request a proof of concept on your own SAP data and workflows.
+1 (415) 226-9867
Vigience, Inc.
Vigience Overcast is SAP certified
