Let’s be clear about what this server is, because the answer disappoints in a useful way.
The Smartsheet MCP server connects an AI client to Smartsheet. Nothing more. It doesn’t reach into Salesforce, and there is no Smartsheet-side integration hiding inside it.
What makes the hub pattern work is that the connection lives in the client, not in the server. If your assistant also has a connector for the other system, then both are in the same context and the assistant can move between them. That is where "Smartsheet plus Outlook plus SharePoint" comes from: several connectors in one client, not one connector that knows about all of them.
Which puts the real question somewhere most people do not look first:
- What can my client connect to? → the client's connector list
- What can it do in Smartsheet? → this server's tools
- What has to be scheduled or event-driven? → the APIs, Smartsheet’s and the other system’s
The third line is the one that catches people. Anything that has to run at three in the morning, anything triggered by a record changing rather than by a person asking, anything that must produce an identical result every run, is not a conversation. Two-way syncs, nightly loads and warehouse exports are integration work and they stay integration work. The assistant is very good at the ad-hoc half and it is not a replacement for the scheduled half.
Two honest limits worth naming rather than discovering:
Resource Management is a separate API and is mostly outside this server. The one exception is scenario planning, which reads from the Resource Management service. Assignments, time entries and leave are still API-only. It has come up here already and it is a known request rather than a secret.
The full-table extract, the kind Power BI and a warehouse want, is an API job. The MCP server is the wrong shape for it.
If you are running the hub pattern, what is on the other side, and which half of it is conversation and which half is scheduled code?
