Apps and connectors
What Vectra plugs into, and how installing a connector actually works.
Settings → Apps is the directory of everything Vectra connects to. Each card opens an install dialog that gets you to a working connection without leaving the page, and links here for the long version.
Three kinds of connector
| Kind | What it is | Examples |
|---|---|---|
| AI assistant | Speaks Model Context Protocol. Reads your fleet, and can act if you let it. | Claude, ChatGPT |
| Rental software | A partner you authorise once. We map trackers to their inventory. | RentalTide |
| Developer tool | Your own code, against the REST API or the same MCP server. | REST API, Cursor, Claude Code |
Installing one
- 1Open Settings → Apps
Cards show a status where we can actually check one: RentalTide reports a live connection, and anything MCP tells you if the account has no API key yet.
- 2Press Install
The dialog holds the steps for that specific app, plus the config block to copy.
- 3Create a key from the dialog
It is scoped to that connector and named after it, so you can see in the API keys list which assistant is holding which key.
- 4Paste the config into the app
Every MCP client wants the same two things: the server URL and your key in the X-API-Key header.
There is no separate connector credential to manage. Revoke the API key under Settings → API keys and that app loses access immediately — nothing else to undo.
Read-only or control
The install dialog offers a control toggle. Left off, the key carries only read permissions and the assistant physically cannot change anything. Turned on, it also gets storage mode and the engine cut-off — which still needs an explicit confirmation and still refuses while the asset is moving.
Zapier, webhooks and Slack are on the way. If you need one of them sooner, or something else entirely, mail support@vectragps.com and say which — the list is driven by what operators ask for.