Provides tools for interacting with SAP Ariba, enabling retrieval of event summaries and other operations via the SAP Ariba API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@SAP Ariba MCP Server Get event summary for doc_id 12345 with user jdoe, password_adapter default, realm test"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Related MCP server: caseware-kb
To run the mcp sevre locally opn the terminal and type uv run main.py You can in the in the terminal Uvicorn running.
Now open one more terminal and tye the command uv run mcp dev main.py It will opne the inspector, just paste the inspector url in the brower.
Set the parameters as below -
- Transport Type as STDIO.
- Command as UV.
- Arguments as run --with mcp mcp run main.py.
Now open the ⚙️ Configuration and fill the below fileds -
- Inspector Proxy Address as http://127.0.0.1:6277 you can find the terminal as shown in the screenshop
- Proxy Session Token - copy session id form the terminal ans paste.
Now click on the connect button and it will connect to MCP server. Now you see the resources, prompts, tools now click on tools the choose List Tools and you can see the tool that you have specified.
Provie the tool get_event_summary and provide the below inputs -
- doc_id
- user
- password_adapter
- realm
and click on run tool and see the output.
> Conclustion - We have locally tested the MCP server successfully. Lest inspect the remotely deployed MCP servr.
Run the inspect command in terminal uv run mcp dev main.py
Set the parameters as below in the inspector as belwo-
Transport Type as STDIO.
Command as UV.
Arguments as run --with mcp mcp run main.py.
Retrieve supplier bids for a sourcing event.
Args: doc_id: Document ID (e.g., 'Doc1213131') user: Username (e.g., myuser) password_adapter: Password adapter (e.g., 'myadaptor') realm: Realm name (e.g., 'myrelm')
Inputs: user (required), realm (required), doc_id (required), password_adapter (required). Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
With only one tool, there is no possibility of confusion or misselection between tools. The single tool's purpose is clearly defined.
The one tool name (get_event_summary) follows a clear verb_noun pattern and is internally consistent. Since there are no other tools, there are no naming inconsistencies.
A single tool is far too few for a server named 'SAP Ariba MCP Server,' which implies a broad procurement/sourcing domain. This is a significant under-provisioning for the apparent scope.
The tool only retrieves supplier bids for a sourcing event. There are no operations for managing events, suppliers, bids, or any other typical lifecycle actions, making the surface severely incomplete for the stated domain.
Pay-per-result SAM.gov contracts, SEC EDGAR filings, USAspending awards and GLEIF LEI lookups.
Document inventory, extraction, summaries and comparison with source quotes and usage billing.
SAM.gov contract opportunities and entity lookup (BYOK) plus USASpending federal award data.
isolved and ApplicantPro jobs, tenant discovery, and change detection as an MCP server.