MCP & AI Agents
FlowPSA has its own Model Context Protocol server. Any client that can call tools, such as Claude, ChatGPT, Codex, Gemini, or a local model, uses the same capabilities as the portal. There is no copilot SKU.
At Acme MSP, one agent token triages the Service desk queue for clients like Acme Corp while people keep every approval.
Connecting
The FlowPSA MCP endpoint is /api/v1/mcp on your FlowPSA address, for example https://portal.example.com/api/v1/mcp. It uses stateless Streamable HTTP with bearer authentication. Give each agent its own token with the agent role.
FlowRMM has a separate MCP server. Configure two named connections in your agent client, one for each product. Neither proxies the other, and their permissions stay separate. See FlowRMM Integration.
What agents can do
FlowPSA exposes over 100 typed tools, including:
- Tickets:
list_tickets,get_ticket,create_ticket,append_note,assign_ticket - Dispatch:
get_next_ticket,claim_next_ticket,get_queue_health - Memory and outages:
find_similar_resolutions,detect_incident_storms - Resolution:
check_resolution_gate,request_resolve,link_ticket - Time:
log_time,get_weekly_timesheet - Work graph: tasks, work orders, projects, change requests, and problem records
- Billing:
preview_invoice,request_invoice - Assets, companies, contacts, knowledge, SLA policies, and governance settings
A typical agent loop
- Claim the next ticket with
claim_next_ticket. - Read the ticket, its SLA, and the asset.
- Check resolution memory and client SOPs.
- Remediate in FlowRMM under FlowRMM's own approvals, then link the action or session to the ticket.
- Run
check_resolution_gate. - Propose the resolution with
request_resolve. - Preview time for billing.
What agents cannot do
| Approval | Who may decide | Second person? |
|---|---|---|
| Resolve (without verified evidence) | Admin, Operator | No |
| Customer-visible note from an agent | Admin, Operator | No |
| Billable agent time | Admin, Operator, Billing | No |
| Change request | Admin, Operator | Yes |
| Invoice posting | Admin, Billing | Yes |
The agent role cannot decide any approval, cannot reopen locked timesheets, and cannot claim administrator authority through tool arguments. Agents are assignable like people and are never billed as seats.
Related guides
Want hands-on help? Book a demo or get in touch.