Create Accountor Login
Docs

Your Services for Clients

Part of the MountDev Ops Verticals documentation. Updated November 18, 2026

MountDev Ops Verticals documentation | Updated November 18, 2026

Your Services for Clients is where offering your own tools to your clients' apps and AI assistants is managed. It is the second page of Verticals, and Services in a vertical's column opens it.

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.

What It Does

Your Services for Clients is the publisher's side of publishing, the same one that was Publish in Integrations. You offer your own modules and actions to your clients' apps and AI assistants through the same connections, permissions, and docs the product's apps use (Publishing). Nothing about how publishing works changed when it moved: the same actions (core.publish.*), the same permission (Publish modules and actions to your customers, and decide who gets them), and the same results.

The page has four parts:

  • Your Publisher Name: the name your permissions start with, the name your clients see, and an optional branded address. Your endpoint, the address your calls go to, is a Connected Service called Published Service Endpoint, with its key sealed in your account.
  • Modules and Actions: add a module, add its actions, turn each on or off, and see earlier versions. A new module or action starts off. Turn one on and your clients see it in both the API and the MCP, as soon as their copy is updated. Turn it off and it goes from every list and is refused by name.
  • Clients and Usage: which accounts you publish to, which of your permissions their connections hold, and how many calls they made. Counts only, never what was sent or answered.
  • Docs for Your Clients: a page for each module, a Permission Finder, and the machine-readable index and llms.txt.

Who Sees It

Owners, admins, and anyone whose role allows publishing. Everyone else is told to ask one of them. An AI agent, an API key, or a connection never publishes on its own.

Inside a Vertical

Services in a vertical's column opens this same page with that vertical picked, so Clients and Usage lists only that vertical's clients. There is one page, never a copy, so nothing here is in two places.

Where Services from Your Providers Went

Services From Your Providers is what your company receives, so it stays in Integrations (and in Settings, Connections until your company adds Integrations), for anyone whose role allows managing providers. It is not part of Verticals.

The Old Publish Address

Every old address still opens the right page: Integrations, Publish, and Settings, Connections, Publish. Someone who may publish lands on Your Services for Clients. Someone who may only manage providers lands on Services From Your Providers. If Verticals is turned off, an owner or admin is told and can turn it on. Search finds Your Services for Clients and Services From Your Providers by name, and by the old word Publish.

Ask Us Anything

We’d love to hear from you!