01
list_demo_types
See the sales demos Vektor currently offers and what each conversation covers.
Vektor MCP
Access token requiredHelp a freight team choose the right product conversation, check real calendar openings, and book the selected time without leaving Claude.
The first release does one job: product demo scheduling. It does not expose customer records, freight data, rates, internal calendars, or Vektor account actions.
Ask Vektor for an approved connector token, then paste these commands into your terminal. The final command checks the saved connection.
Request a connector token from Vektor. Tokens are not published in this documentation.
Export the token in your current shell and add the remote HTTP server.
Verify that Claude can reach the saved Vektor connection.
Treat the token like a password. Do not commit it to a repository, paste it into a shared document, or send it in chat.
export VEKTOR_MCP_TOKEN="<TOKEN>"
claude mcp add --transport http vektor https://vektortms.com/api/mcp/scheduling \
--header "Authorization: Bearer ${VEKTOR_MCP_TOKEN}"
claude mcp get vektorFour small tools keep the conversation in order, from choosing the session to confirming the booking.
01
See the sales demos Vektor currently offers and what each conversation covers.
02
Match a carrier, broker, or shipper to the right session. Carrier fleet size sets the depth.
03
Read real open slots from the Vektor calendar in the visitor's timezone.
04
Create the meeting only after the visitor confirms the time and contact details.
The scheduling server accepts contact details only for a confirmed booking. Tool analytics contain event slugs, counts, and timing, never names, email addresses, phone numbers, notes, meeting links, or booking management links.
Read tools return demo metadata and open times, not host calendar details.
Booking confirmations and meeting links are delivered by email, not repeated in the model response.
Recruiting and customer training events are outside the public connector allowlist.
Tell us how you plan to use the Vektor connector. We will confirm the current access and rollout path.