Private integrations

Your integration should belong to your account, not the public tool catalog.

Current availability: operator-assisted onboarding. You can submit, list and cancel an account-private hosting request. Provisioning, private tool discovery and execution are not yet self-service. No request launches a server or starts billing.

Choose how to host

• Managed: request a dedicated runtime. Before activation we review the integration source, permissions, resource limits, region, persistence and costs with you.
• Bring your own server: submit your HTTPS MCP endpoint. It is recorded privately, not fetched or added to the shared registry. Reachability, ownership and authentication are reviewed before connection.

Onboarding

1. Sign in through your Distributed account and choose a listed plan. Final inclusions and hosting costs are confirmed before activation.
2. Submit the request below with a token authorized for your account. For multiple accounts, select an authorized account with X-DSCO-Account-ID.
3. We review the request. Do not submit passwords, mailbox contents or API keys. Credentials belong in an account-scoped secret store during approved setup.
4. Activation requires separate per-account runtime state, credentials and network boundaries, plus tests that another account cannot discover or execute your tools. A tenant header alone is not isolation.
5. After approval and deployment, receive the private endpoint and explicit access grants. Public listing is a separate opt-in; requesting hosting never publishes your integration.

Submit a request

curl --fail-with-body -X POST \
  'https://tools.distributed.systems/api/v1/me/private-integrations' \
  -H "Authorization: Bearer $DSCO_TOOLS_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"name":"My mail integration","plan":"pro","hosting":"managed","integration":"cloudmail","idempotency_key":"my-mail-request-1"}'

A successful submission returns HTTP 202 with status: requested, provisioned: false and billing_started: false. Reuse the same idempotency key only for the same request.

For an existing server, use hosting: bring_your_own, integration: custom_mcp and an endpoint such as https://your-server.example/mcp. Do not put credentials in URLs. Optional managed image references must be digest-pinned; submitting an image does not execute it.

Track or cancel

• GET /api/v1/me/private-integrations — your account's requests only.
• GET /api/v1/me/private-integrations/{request_id} — request status.
• POST /api/v1/me/private-integrations/{request_id}/cancel — cancel an unprovisioned request; this is not deletion of a running server.

CloudMail activation boundary

CloudMail is not enabled for arbitrary customers. It requires an approved account, principal, client and dedicated mailbox endpoint binding. Read, send, organize and administrative permissions are separate. Send acceptance is not delivery confirmation.

View the $20, $100 and $500 monthly plans · API reference