Five jobs it does well: the question nobody reported on, the draft from a live record, the small update that follows a decision, the answer spanning two systems, and the handover. One job it gets asked to do constantly and should not.
They all share a shape. The question is different every time.
1. The question nobody built a report for
Which deals went quiet after the proposal. Which clients have not been contacted since the review. Which objectives slipped this month and who owns them.
Reports answer the questions somebody anticipated when the report was built. These are the questions you have right now, and there are more of them than any reporting backlog can cover. This is the job that makes the connection worth setting up.
2. The draft that starts from a live record
A follow-up email that refers to what was actually discussed. A client update built from what actually changed. A summary of the quarter that uses the real numbers.
The value is not the writing. Models have been able to write for years. The value is that the writing starts from the current record instead of from what somebody remembers, which is the difference between a draft you edit and a draft you rewrite.
3. The small update after the decision
You ask what is behind. You decide what to do about it. The action gets created without opening another tab and retyping what you just said.
This only works where the vendor publishes write actions, and many do not. It is also the job with the highest time saving per use, because the alternative is a person transcribing a conclusion that already exists.
4. The answer that spans two systems
What did this client pay us last year, and what have we actually delivered against the plan. One half is in a billing system, the other in a delivery system, and the question has never had a home.
Nobody builds a report across two systems for a question asked twice a quarter. An assistant with both connections answers it in one go.
5. The handover
Someone is away, or has left, and their work has to be picked up. "What is the state of these twelve accounts and what has been promised" is a reconstruction job that normally takes a day of reading.
The job it should not do
Anything on a schedule with nobody present.
An MCP connection is dormant until asked. It does not watch, it does not run overnight, it does not fire on the 15th. Every team that has been disappointed by one of these connections asked it to be an integration, and it is not that and does not pretend to be.
| Want this | Use |
|---|---|
| The same thing, on time, unattended | An integration or scheduled job |
| A different question each time | An MCP connection |
| Both, aimed at different problems | Most businesses, honestly |
What decides whether you get all five
The published action list, which is the vendor's choice and not the assistant's. A short read-only list gives you jobs one, two and four. Writes give you three. Nothing gives you the scheduled thing.
Ask any vendor for the list before setting it up. It takes a minute to read and tells you which of these five you are actually buying.
Where Empiraa sits
Empiraa Signal is a CRM and more. It is also the B2B prospect database, the enrichment, the email sequences, the booking link and the proposal tool, in one system with unlimited users on every plan, which matters here for a dull reason: jobs one and four get much easier when the answer does not have to be assembled from four separate subscriptions. Signal's own MCP is in build and not shipped at the time of writing. Empiraa GPS shipped one in version 1.22, so the access model is already published and running.
Related reading: what an MCP server is, and what it is not, and how MCP works in five steps.
MCP or integration is the four-question version of the choice above.
