Create Accountor Login
Docs

Client Feed

Part of the MountDev Ops Workspace documentation. Updated November 17, 2026

MountDev Ops Workspace documentation | Updated November 17, 2026

The client feed is how a client account gets its own pages from its provider without anything passing through a third place. When a client opens Requests, Billing, or another page the provider answers, the client's workspace asks the provider's workspace for exactly that client's page, and the provider answers for that client only. Your account keeps its own copy of what your provider answered.

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 6,565 automated checks before it ships, and every screen change is walked through before release.

How It Works

  • A page is asked for. Your workspace sends your provider one question: the name of the page, and what you chose to ask (a filter, a number). Nothing else leaves your account.
  • The provider answers for you only. Your provider's workspace works out the answer for the company whose Client Account is your account, and sends it back. It cannot answer for another client, and another client's question never reaches your account.
  • Your account keeps the answer. The last answer for each question is kept in your account. Every screen of yours that shows it updates at once when a new answer arrives. A closed account reads what it already holds and asks for nothing new.
  • A change is done once. When a page lets you ask for one change, such as opening a request, your account records who asked, sends it once, and your provider answers once. If the same request arrives again, your provider gives the same answer and does nothing twice.

Questions and answers are kept to plain text and numbers, and an answer is limited in size. A page that has more to show is shown in parts.

Turning It On

Until an owner or admin turns the feed on for an account, its pages keep working the way they do today. Turning it on moves only the pages your provider has built for the feed, and a page not built yet keeps working the old way. People who hold Choose how clients get their pages (owners and admins to start, and any role that holds it) turn it on or off (action core.feed.set, MCP tool client_feed_set).

What a Provider Sees

A provider sees the question your account sent and nothing else of your account. It never reads your records. It keeps only the answer it gave to a change you asked for, so a repeat is not done twice.

Actions

  • core.feed.page shows what your account holds for a page. Anyone who may use the page. People only.
  • core.feed.refresh asks your provider for a page again. The same question is not sent twice within 20 seconds. People only.
  • core.feed.do asks your provider to make one change for your account. People only.
  • core.feed.change shows what happened to a change you asked for. People only.
  • core.feed.status says whether your pages come from the feed. People only.
  • core.feed.overview lists the pages your account answers for its clients and whether the feed is on, with counts only (MCP tool client_feed_overview).
  • core.feed.set turns the feed on or off (MCP tool client_feed_set).

An AI agent or API key never asks for a change on a client's behalf, and never signs anyone in or pays anything.

Emails

The client feed sends no email.

Export

What your account holds from its provider is part of Export Everything.

Ask Us Anything

We’d love to hear from you!