Public Shared Events MCP guide

Connect an MCP client to public Split and Schedule tools on this client domain

This MCP server exposes the same public shared-event capabilities as tools. It is separate from the merchant/admin MCP service.

MCP endpoint

https://onepay.tabsystems.tech/mcp

Tool setup

Configure your MCP client with this client-origin URL only. The server discovers the available tools after connecting; do not add account credentials or private event values to the configuration.

{
  "mcpServers": {
    "onepay-shared-events": {
      "url": "https://onepay.tabsystems.tech/mcp"
    }
  }
}

Ownership and recovery

MCP clients should preserve the privacy of event links and recovery material. Browser ownership sessions do not replace the owner's recovery process when moving between devices.

Treat every event link and recovery value as private. Share only the event link needed for collaboration, and keep recovery material out of messages and logs.

Revisions and conflicts

For content changes, read the latest event and provide its current revision. On a conflict, fetch the event again before choosing whether to retry.

Rate limits

MCP calls use the same protections as the REST API. Back off when the service reports a limit instead of retrying immediately.

Expiry

Shared events expire automatically. Reading an event or exporting it does not extend its lifetime, so copy any information you need before expiry.