Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vaultgraph.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

VaultGraph is a hosted, multi-tenant MCP gateway for e-commerce merchants. It gives merchants one managed protocol layer to expose their catalog, cart, checkout, and orders to AI agents — without handing customer, order, or checkout ownership to a third party.

​
How it works

The integration goes one way: VaultGraph posts to one HTTPS endpoint on your storefront. Your storefront never calls VaultGraph.
  1. You configure a shop and a deployment in the portal. Each deployment is one MCP endpoint.
  2. You expose one HTTPS endpoint on your storefront and register its URL + signing secret on the deployment. The gateway POSTs to that endpoint on every tool invocation. Use createAdapterHandler — it’s the entire merchant integration in one file.
  3. Agents connect to the deployment’s MCP endpoint with the deployment’s API key. They get typed catalog search, cart, checkout, and order tools out of the box.
Customer, cart, order, and checkout records stay in your infrastructure; the gateway is stateless over your backend.

​
Integrate your storefront in one file

Implement only the methods you support with createAdapterHandler — it handles signature verification, routing, and serialization, and anything you skip auto-returns not_implemented. The SDK reference has the complete, copy-pasteable handler. You do not call any VaultGraph REST endpoint from your storefront. Catalog/cart/order tools are served to agents — your job is to implement the methods VaultGraph calls.

Core Concepts

Organizations, shops, deployments, commerce backends, and API keys.

Setup

Create a shop, a deployment, and connect your storefront.

SDK

createAdapterHandler — the entire merchant integration in one file.

Adapter protocol

Wire contract for the requests VaultGraph posts to your endpoint.