Agents & MCP
How AI agents relate to staff users and the MCP server.
SolutionDesk treats AI agents as staff principals when they connect over MCP — not as portal end-users.
Mental model
| Actor | Identity | Entry |
|---|---|---|
| Human staff | User + membership | Login → dashboard |
| AI agent | Same staff User via OAuth to MCP | MCP client → /v1/mcp |
| Acme end-user | EndUser | MagicLink → portal only |
An agent never “logs in as Acme.” If it needs to file work for Acme, it uses staff tools (create_ticket with company) or the host Integration API from your backend.
Why MCP is separate from the Host API
- MCP = interactive agent tooling with a human staff session (OAuth).
- Host API = automation with a workspace API key (no human in the loop for each call).
Both must respect tenant isolation and ticket visibility. Product how-to: MCP for agents and Host SaaS API.