StackTether

StackTether features

StackTether gives an MSP's AI assistants 20 read-only tools over Kaseya BMS and Autotask PSA, and gives the MSP's admins full control over who can use them, from which AI app, and how much. Everything on this page exists and works today.

Read-only PSA tools

Tool names are vendor-neutral: the same tool works on Kaseya BMS and on Autotask, and the AI never needs to know which PSA you use. Lists are capped (25 results by default) and say when more exist; long text such as ticket descriptions is shortened and labelled.

The 20 tools available to AI apps today
ToolWhat it answers
psa_search_ticketsFind tickets by client, status, keyword or assignee, newest first. "Me" means the signed-in tech's own tickets.
psa_get_ticketOne ticket with its details, recent notes and checklist.
psa_get_ticket_historyWho changed what on a ticket, and when.
psa_list_ticket_time_entriesTime logged on a ticket.
psa_list_related_ticketsTickets linked to a ticket.
psa_list_ticket_optionsValid statuses, priorities, queues and similar values, so the AI filters correctly.
psa_search_clientsFind clients (companies).
psa_get_clientOne client with its details and business locations.
psa_list_client_notesA client's notes (sales and finance notes are left out).
psa_search_contactsFind contacts at your clients.
psa_search_assetsFind assets: devices and configuration items.
psa_get_assetOne asset with its details and recent tickets.
psa_search_projectsFind projects.
psa_get_projectOne project in full.
psa_search_tasksFind project tasks.
psa_search_contractsFind contracts (never prices or billing terms).
psa_search_my_time_entriesThe signed-in tech's own time entries.
psa_list_scheduleScheduled visits by day.
searchChatGPT's standard search tool over tickets and clients (used by deep research).
fetchChatGPT's standard fetch tool: one ticket or client by ID.

A few tools are not offered by Kaseya BMS's API; when you also have a second PSA connected, StackTether asks that one instead. The full list with limits is in the support guides.

Two PSAs at once

An MSP can connect a primary and a secondary PSA, for example during a migration from one to the other. Searches ask the primary first and then the secondary, and every record ID carries a short prefix (bms: or autotask:) so the AI always knows where a record came from.

Team and access control

  • Invite-only accounts. Nobody can sign up without an invite from an admin of their MSP.
  • Roles. Admins manage the team, connections and AI apps; techs use the tools.
  • Per-member vendor access. An admin decides which connected systems each member can reach through AI. New members start with none.
  • Vendor credentials in a vault. Saved only after a passing connection test, encrypted, never shown again (the portal shows a fixed mask).
  • Account recovery for admins. Reset a password or 2FA, sign a member out everywhere, pause or remove a member.

AI app control

  • Allowed apps per MSP. Each supported AI app has its own switch, and every switch starts off.
  • AI apps per person. Admins can allow an app for some members and not others, or switch all AI access off for one person.
  • Consent with 2FA. Connecting an AI app opens a StackTether approval page that shows the app's name and needs a fresh 2FA sign-in.
  • Short approvals. Approvals last 30 days for cloud AI apps and 7 days for apps on a tech's computer, and end after 14 idle days. Access tokens live 15 minutes.
  • See and revoke connections. Admins see every connected app per member and can disconnect any of them.

Audit log of every AI tool call

Every tool call gets exactly one audit entry, including calls that were refused: the tool, the person, the AI app, the time, the network address, the outcome and the IDs of the records that were read. The audit log never holds ticket text or other record content. If the audit entry cannot be written, the AI gets no answer. Admins read the log in the portal; members see their own history.

AI safeguards

  • Call budgets. 60 tool calls a minute per tech, 1,000 vendor requests an hour per tech and 2,000 per MSP. When a budget runs out, the AI is told exactly how long to wait.
  • Unusual-activity checks. StackTether compares how many records each tech pulls with that tech's own normal pattern and can warn, slow down or pause until an admin reviews.
  • Kill switches. An admin can stop all AI access for the MSP at once, and the platform has its own emergency stop.
  • Network rules. Calls for Claude are accepted only from Anthropic's published network range. Apps on a tech's computer can be limited to a country list, with temporary travel overrides, and a new network raises an alert.
  • Step-up 2FA. Sensitive actions such as handing over the primary admin role or resuming paused AI access need a fresh 2FA code.
  • Untrusted vendor text. Ticket text is passed to the AI clearly marked as data, not instructions, and cannot fake StackTether's own labels.

Sign-in and accounts

  • Two-factor authentication with an authenticator app for every user, enforced in the database itself.
  • Lockout after repeated wrong passwords, rate limits on sign-in and 2FA, and a bot check on sign-in forms.
  • Portal sessions are tied to their network; a change of network signs the portal out (AI connections are not affected).
  • Light and dark themes, and every page works on a phone.

Data handling and retention

Sensitive fields are never mapped into a tool at all: passwords and keys stored on assets, Social Security and tax numbers, dates of birth, bank and card details, prices, costs, rates and billing amounts, and home addresses. Audit and activity logs are kept for one year; unused accounts, closed invites and short-lived counters are cleaned up on fixed schedules. Details are on the security page.

Feature questions

Does StackTether have write tools?
Not today. All 20 tools only read. If write tools are added later, each will be off for every user by default and an admin will have to switch it on per tool and per person, with a fresh 2FA check.
Can I limit which clients' data a tech can see?
StackTether limits access per connected system, and your PSA API user's own permissions limit what that system returns. Per-client limits inside a PSA follow the API user's security level in the PSA.
Can I export the audit log?
Admins can read and filter it in the portal today. Export and forwarding to your own SIEM are on the roadmap.

See it with your own PSA

StackTether is free during the Founding MSP beta. Founding MSPs get setup help and a direct line to the people building StackTether.