Connecting Your Visitor AI Client

Time to complete: 2–5 minutes
Prerequisites: A work email address.

Overview

This page walks through connecting your AI client to the Visitor AI Connector. The Visitor AI Connector uses OAuth — you'll sign in with your work email, and your identity is carried through to every Trust Center you visit.

Server URL:

https://visitor-mcp.conveyor.com/mcp

📘
Enterprise accounts
Some AI providers (ChatGPT Business, Claude Enterprise, etc.) require an organization admin to register custom connectors before individual users can use them. If the Visitor AI Connector doesn't appear in your connector list after following these steps, ask your IT admin to add it once for the whole organization.

Option 1 — OAuth (Claude, ChatGPT, Any Modern MCP Client)

For OAuth-capable clients, add the server URL as a custom connector or app. The client handles the rest of the flow — you'll sign in with your work email and you're ready to start visiting vendor Trust Centers.

Once the connector is registered, connect from inside your client:

Connect in Claude

Select the + icon → Manage connectors.

Select the Visitor AI Connector and click Connect. Since it's a custom connector, it appears under whatever name your admin gave it when registering it.

Connect in ChatGPT Business

Search for the Visitor AI Connector in the app list.

Select Connect.

Option 2 — JSON-Configured Clients (Cursor, Claude Code, etc.)

Add the following configuration to the client's JSON settings:

{
  "mcpServers": {
    "conveyor-visitor": {
      "url": "https://visitor-mcp.conveyor.com/mcp"
    }
  }
}

For Claude Code, you may also run the following command to add it to your MCP server list:

claude mcp add --transport http "Conveyor Visitor" https://visitor-mcp.conveyor.com/mcp

Your client will prompt you to sign in with your work email when you first use the connector.

Common Questions

Q: Do I need engineering help to set this up?
A: No. Add the server URL as a custom connector and the client handles the rest — no custom integration, no API scripting.

Q: My client connected, but the assistant isn't using it. What now?
A: Ask it explicitly — e.g. "Using the Visitor AI Connector, find Acme Corp's Trust Center and show me their documents." Assistants with many connectors sometimes need a nudge toward the right tool.

Q: Do I need an API token?
A: No. The Visitor AI Connector uses OAuth to verify your identity via your work email. There's no API token to generate or manage.

What's Next?

Using the Visitor AI Connector — example workflows to try with your newly connected client.

Need help? Visit the Integration Issues guide or contact [email protected].