AI agent access
Connect an AI agent to your firm
You can let ChatGPT, Claude, Microsoft Copilot or another compatible AI agent work with your firm's client requests, without giving it an API key and without giving it authority Vertical Flows keeps for you.
1. What this does
Once connected, you can ask your AI agent about your firm's work in plain language — what needs attention, what a client has sent back, where a request has got to — and it reads the answer from Vertical Flows rather than guessing. You can also ask it to prepare a client request or a follow-up for you to review.
The agent asks Vertical Flows for outcomes. Vertical Flows decides what is allowed. Your firm membership, your role, your permissions and your approval step all stay exactly where they were.
2. Connect an agent
The connection starts in your AI agent, not here. That is deliberate: only you can add a tool to your own AI account, and no website should be able to do it for you.
In your agent, add a connector or custom tool using this server address:
https://verticalflows.com/api/mcp
Your agent will send you to Vertical Flows to sign in, choose which firm the agent may work with, and approve its permissions. You will land back in your agent once you approve. There is no API key, no configuration file and no terminal command.
You can also copy the same address from Settings → Connections → Agent access inside Vertical Flows, where every connection is listed and managed.
3. Permissions
You choose what a connected agent may do, and you can change it or take it away at any time. Permissions are granted per firm, so an agent connected to one firm cannot see another.
View lets the agent read scoped work, request status and evidence for the firm you selected.
Prepare lets the agent draft a client request or a follow-up for you to review. Nothing is sent until you approve it.
Act lets the agent approve a prepared request or follow-up on your behalf, and records every approval as activity you can see. Only a firm owner or administrator can grant Act, and it is available only where Vertical Flows has switched it on. Act still sends nothing: it approves inside Vertical Flows, and delivery remains a separate, governed step reported by the request's own status.
4. What an agent can never do
A connected agent cannot send email to your clients, write to Xero or another connected system, charge anything, change your settings or secrets, see another firm's data, or give itself more permission than you granted. These are not settings you can loosen by accident; they are boundaries the connection does not cross.
An agent also cannot tell you something happened unless Vertical Flows says it happened. Where an agent reports that a request was sent, that claim comes from the request's own delivery status, not from the agent having asked.
5. Manage or revoke access
Every connection appears in Settings → Connections → Agent access with the agent, the authorised firm, the permissions granted, who connected it, when it was last used, and its recent governed activity.
Test connection checks the connection against your real scoped work and reports honestly when there is nothing needing attention. Change permissions adjusts what the agent may do and requires it to reauthorise. Revoke access stops it immediately, everywhere.
Access also ends on its own when it should. A short-lived credential expires in minutes, a change to your role or firm membership takes effect on the agent's next request, and removing Act removes it from a connection that already held it.
6. Technical details
Vertical Flows implements the Model Context Protocol over Streamable HTTP at https://verticalflows.com/api/mcp, supporting the current protocol revision and the earlier ones so agents that have not migrated keep working.
Authorisation is delegated OAuth 2.1 with PKCE. Public clients receive no client secret, access tokens are audience-bound and short-lived, refresh tokens rotate and reject replay, and every tool call re-checks your firm membership, role and permissions against current records rather than trusting a token.
Discovery documents are published at /.well-known/mcp/server-card.json, /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server. See our Security page for how approval, tenant boundaries and audit evidence work more broadly, and our Privacy Policy for how information is handled and stored.
7. Support
If a connection will not complete, or an agent reports something you cannot see in Vertical Flows, contact us at support@verticalflows.com with the name of the agent and the firm you were connecting. Do not send access links, tokens or client documents by email.