Peon

Agencies, consultants, and freelancers often work across several accounts in the same apps. Connecting an AI assistant to those apps is only part of the problem. It also needs to know which account belongs to the client in the conversation.

Peon makes the client the starting point. A client record holds their name, company, aliases, and notes, alongside the app accounts assigned to them. The assistant can resolve that context before discovering tools or taking an action. If a name is ambiguous, the workflow asks for clarification instead of choosing an account by guesswork.

The dashboard brings client records, connected accounts, access settings, and agent connections into one place. Each client has one selected account per app, and the same account can be attached to several clients when that reflects how the business works.

A shared Model Context Protocol interface makes that setup available to compatible assistants. Five focused tools cover finding a client, reading their context, discovering actions, collecting updates, and executing a selected action. Tool discovery stays tied to the client’s connected apps.

Permission to use an app does not automatically mean permission to use everything in it. Peon separates the actions an assistant may perform from the records it should receive. Full, read-only, and curated modes control the available tools; client identities and selected resources define the data boundary.

For example, access to a shared account can still need to be limited to one client’s resources. Peon reports whether a response was narrowed, filtered, left unbounded, or could not be matched. That disclosure gives the assistant context for what it can safely conclude from the result.

A provider response carries more than its data. Peon includes the client context, an execution receipt, item counts, pagination, and any truncation. A partial result should be recognisable as partial, rather than looking like a complete account of the client’s work.

The update-collection tool can gather read-only results across connected apps while retaining partial successes. This supports everyday tasks such as preparing for a client meeting or assembling a status update, without requiring every provider to respond successfully at the same moment.

Peon’s role is to connect an agent’s request to the right client, account, permission, and response. The assistant handles the conversation; the provider handles its own application. Keeping that division clear makes the product easier to explain and the route taken by an action easier to follow.