Before you connect
- You need a Vight account with access to the workspace whose calls and tickets you want to search.
- The connector currently exposes two tools: searching calls and tickets, and fetching one result in full. It does not create, edit, or delete anything in Vight.
- Only calls the authenticated Vight member can already see in the product are returned, and tickets only for a member with the Tickets permission. The connector does not expand what you have access to.
MCP server endpoint
The connector is hosted at https://app.vight.ai/api/mcp.
There is nothing to install locally. Point an MCP-compatible client at this URL and authenticate with OAuth. No API key is needed.
Connect your account
- Find Vight in your AI platform's connector or MCP directory (or add a custom connector pointing to
https://app.vight.ai/api/mcp). - Select Connect or Add.
- Sign in with your Vight account credentials when prompted and approve the requested access.
- Return to the AI platform once authorization completes.
Labels and steps vary slightly by client (Claude, Claude Code, Claude Desktop, etc.). Consult your client's documentation for its specific connector setup flow.
How to use it
Ask your question naturally. The host AI calls Vight's tools when the answer likely lives in a past call: a client conversation, a specific date range, or a topic that came up on a call.
Example requests
- "Did anyone from Acme mention wanting to upgrade their server this quarter?"
- "Find the call where we walked a client through MFA setup last week and pull the relevant part of the transcript."
- "Search calls with Contoso between March and June for anything about their renewal."
Tool catalog
| Tool | What it does | Annotation |
|---|---|---|
| Search | Searches the calls the authenticated Vight member can discover and their organization's PSA tickets, filterable by keyword, client name, a start/end time range, and open or closed status. Returns matching records for the assistant to inspect further. | readOnlyHint: true |
| Fetch | Retrieves a specific call or ticket returned by Search: a call with a bounded page of its transcript, a ticket with its header, description, summary, notes, and time entries. Supports paging through longer records via an offset. | readOnlyHint: true |
Both tools are read-only. There are no write, delete, or account-modifying tools exposed by this connector.
Safety and limitations
- Both tools are strictly read-only. The connector cannot modify, delete, or create tickets, calls, or any other Vight record. Anything the assistant proposes based on a call still requires a human to act on it inside Vight.
- Transcript text returned by Search and Fetch is treated as untrusted spoken source data, not instructions. Wording spoken on a call (by a client, technician, or anyone else) is not honored as a command to the assistant, regardless of what it says.
- Access is scoped to the authenticated user's existing Vight permissions. A call you cannot open in Vight, or a ticket your account is not permitted to read, will not be returned through the connector.
- The host platform's own safety rules and higher-priority instructions continue to apply on top of anything Vight returns.
Data and privacy
Calls processed through Vight (recordings, transcripts, metadata, and AI-generated summaries) and the PSA tickets synced into it are retained according to your organization's configured retention settings in Vight, since the whole point of the connector is to search across that history. You can request deletion of your data at any time.
Where AI processing is involved (for example, generating call summaries), Vight works with third-party AI providers under their enterprise terms; your data is not used to train their models. Vight does not sell personal information, call data, or ticket data to third parties, and does not use third-party tracking or advertising cookies.
Because a call or a ticket note may include anything a client raised, avoid discussing or logging regulated data (e.g. protected health information, full payment card numbers) beyond what your organization's own compliance obligations (HIPAA, PCI-DSS, etc.) already require you to handle carefully. The connector does not add any additional filtering on top of what Vight already applies.
Full details: Privacy Policy · Terms of Service
Permissions
The connector inherits the permissions of the Vight account you authenticate with. It cannot see calls, clients, or workspaces that account doesn't already have access to in Vight, and role-based access is enforced by Vight's servers, not by the AI client.
Troubleshooting
The sign-in window closed before finishing.
Start the connection again from your AI platform and complete the Vight sign-in flow without closing the window early.
Search isn't finding a call or ticket I know exists.
Confirm the record falls within any date range you specified, and that the account you authenticated with has access to that call or ticket (and its client) in Vight directly. Tickets also need the Tickets permission and a board with Ticket Indexing turned on.
I need account or privacy help.
Contact privacy@vight.ai for data questions, or reach the team via vight.ai/contact.
Provider
Vight is operated by Vight, Inc.