2025-03-26) so an agent can drive
order, inventory, product, and returns operations across 180+ integrations for a given tenant.
What it exposes
The registry holds 186 general-purpose tools across 29 categories, plus a small number of tenant-specific operations built for individual accounts.
The remainder are one or two tools each for Amazon, eBay, Etsy, TikTok, MercadoLibre, Shopware,
WooCommerce, products, and audit.
tools/list does not return all of them. It defaults to availableOnly, hiding any tool whose
integration is not configured for the tenant, and the read-only mode and per-tenant blocklist
below narrow it further. Count against your own tenant rather than against this table.Transports
Four, depending on where the agent runs:
The multi-tenant transport takes the tenant per request via
params._meta.tenant.
Connect
Remote (recommended for a hosted server)
stdio (local binary)
Safety controls
The Sync Server has the most developed per-tenant guardrails of any StateSet MCP server, because its tools reach live commerce platforms.Read-only mode
Freeze a tenant so every mutating tool is refused while reads keep working. Useful during an incident.Tool blocklist
Finer-grained than read-only — disable specific tools for a specific tenant and leave the rest available:Both read-only mode and the blocklist are DB-persisted (
mcp_tenant_policy) and rehydrate
into the in-memory registries at startup — so a pod restart mid-incident cannot silently unfreeze
a tenant or re-enable a blocked tool.Result cache
An opt-in per-tenant cache on tool results, for read-heavy agent loops.Operations
Observability config ships with the repo —
docs/observability/mcp-alerts.yaml and
mcp-dashboard.json.