Skip to content

Cursor SAP MCP Server sap_create_escrow_v2

How to: Cursor SAP MCP Server sap_create_escrow_v2

client:Cursor transport:streamable-http tool:sap_create_escrow_v2

Add SAP MCP Server to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "sap-mcp": {
      "url": "https://mcp.sap.oobeprotocol.ai/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something sap_create_escrow_v2 does. Cursor lists the server's tools on connect and calls sap_create_escrow_v2 itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that SAP MCP Server's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

SAP MCP Server will not start until these are set, so sap_create_escrow_v2 never becomes available.

  • SAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE
  • SAP_LOG_LEVEL

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.