Traction Guest MCP. Manage visitor flow and scheduling via chat commands.

Listen up. Your AI client gives your agent total control over every damn visitor operation at a corporate site. You don't have to mess around with web dashboards anymore; you just talk to your agent, and it handles all the backend shit in Traction Guest.

Managing People:
If you need to know who can host visitors, your agent calls list_hosts to show a roster of every registered employee, along with their contact info and department. If you gotta add staff, you've got two ways: you use create_host to onboard one person at a time, or if HR drops a whole sheet of names, the agent runs create_hosts_batch to set up multiple employees in bulk.

Handling Visitors and Scheduling:
For scheduling, your agent handles everything from small chats to massive tours. You can send out a simple invite using create_invite, defining who it's for, when it is, and who the host is. If you need to change that up—say, moving John’s interview or swapping hosts—the agent uses update_invite; you only gotta tell it what changed.

If it was a big deal, like an all-day campus tour, you schedule that with create_group_visit, passing the name, date, expected headcount, host, and location details. You can then modify those major appointments using update_group_visit if something changes on your end. To see what's already booked up, the agent runs list_group_visits.

If you need full background info on a specific group event, it calls get_group_visit by its unique ID.

Scheduling also means canceling stuff. The agent can cancel an entire group appointment using delete_group_visit, but keep in mind that action is permanent. For individual invites, you use delete_invite if you need to wipe out a specific visitor's scheduled slot by its ID.

Before scheduling anything, you gotta nail down the location. You use list_locations to see every office branch configured in the system, getting details like the address and timezone for each. If you just wanna verify the setup for a particular site before running an invite or check-in, the agent calls get_location using that unique ID.

Tracking People On Site:
For real-time tracking, it's simple. When someone walks through the door, your agent logs them in immediately by calling create_signin, registering their name, host, location, and why they’re here. If you need to know who checked in at a specific moment, the agent fetches the full record using get_signin with the sign-in ID.

You can also modify that check-in record later—maybe logging when they actually left or tweaking the visit reason—using update_signin. To see how busy the office is right now, the agent runs list_signins, giving you a current count of everyone who’s clocked in. If you want to know about people who pre-registered but haven't been formally invited yet, check list_registrations.

Security and Audit:
For keeping things secure, your agent lets you list all active security watchlists with list_watchlists, showing the name, description, and how many entries are on it. If you need to add people or groups that should be denied access, the agent uses create_watchlist. For compliance checks and reviewing what happened yesterday, the agent downloads historical activity logs via list_audit_logs.

Other Stuff:
The server also lets you check out available visitor management plans by calling list_packages. Finally, if you need a list of all upcoming individual invites across every single location, the agent runs list_invites, and if you only want details for one specific invite, it uses get_invite.