API / MCP gap: no way to fetch a user's "Open" view (personal + assigned + subscribed)

I run an AI agent on claude that sweeps my Front every morning and surfaces what actually needs my attention, especially activity on our biggest deals. Front is the source of truth for that, so the agent reads conversations through the API (and I looked at the new MCP server too).

The core problem: there's no way to programmatically get my "Open" view, the thing I look at in the UI every day. My Open is the union of my personal inbox + conversations assigned to me + conversations I'm subscribed/following. The first two are reachable. The subscribed bucket is not.

Specifically:

1. follower: search is unreliable. Searching follower:<me> returns only a handful of conversations (4 in my case) when my actual Subscribed bucket in the UI is 23. The conversation object itself correctly lists me under /conversations/{id}/followers, but I can't search or list by it. So there's no way to enumerate "everything I follow."
2. No "Open view" union endpoint. Your own MCP docs confirm this: "There's also no current way to fetch the union of a user's personal inbox plus conversations assigned or subscribed to them. The MCP server returns conversations from the queried inbox only," and "no tools exist to filter by followed/subscribed status in v1."

Here's why it matters in practice. Two of our largest active deals had real movement on a Friday. On both, I was a subscriber/participant, not an @mention, and the threads lived in a teammate's inbox. Because the agent could only reliably read my own inbox + @mentions, it reported "no movement" on both. They were sitting right there in my Open view the whole time. The only reason I caught it was by manually checking.

The workaround I'm stuck with is sweeping teammates' inboxes and content-searching for known client names. That's brittle, and it completely misses any new deal where I'm a silent subscriber.

What I need (any one of these would solve it):

1. An endpoint/MCP tool that returns a user's Open view directly: the union of their personal inbox + assigned + subscribed, filterable by status (open/archived).
2. A subscribed: / follower: search filter that actually returns all of a user's followed conversations, or an endpoint to list the conversations a teammate follows.
3. Per-user OAuth in the MCP is great (it authenticates as me), but it needs a tool that respects my personal Open/Subscribed view, not just per-inbox queries.

Is any of this on the roadmap for the full MCP release or the API? The "built from the ground up, not a wrapper" rebuild sounds like the right moment for it. Happy to be a beta tester. This single gap is the difference between an agent that reliably watches my pipeline and one I can't fully trust.

Thanks.