# Tokeet MCP Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Tokeet MCP

Manage vacation rental properties, guests, rates, tasks and expenses in Tokeet.

- Record: https://musedirectory.ai/connector/tokeet-mcp
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/tokeet/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 3233ms, checked 2026-10-29T10:45:47Z
- Endpoint: https://tokeet.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T12:51:20Z)
- Source: Found in the official MCP Registry (io.usefulapi/tokeet) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Ftokeet

Read and manage Tokeet vacation rental data: properties, availability, rates, guest records with contact details and notes, tasks and expenses. Create guests, add notes and interactions, create and update tasks.

Example request: "Show me all my rental properties and their availability for next month."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Tokeet MCP to help me. It is a free service with an MCP server at https://tokeet.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- tokeet_get_current_user: The Tokeet user the API key belongs to (name, email, role). Login data is never returned. GET /user/me.
- tokeet_list_users: List the team members (users) of the Tokeet account. GET /user.
- tokeet_get_user: One team member by id. GET /user/{user_pkey}.
- tokeet_list_rentals: List the rental properties in the account, sorted by name. GET /rental.
- tokeet_get_rental: One rental property by id (its pkey from tokeet_list_rentals). GET /rental/{rental_pkey}.
- tokeet_list_rentals_by_owner: List the rentals assigned to one owner. GET /rental/owner/{owner_pkey} (Tokeet documents no paging for it: all of the owner's rentals come back).
- tokeet_get_rental_availability: The open and blocked dates of one rental over the next two years. GET /rental/{rental_pkey}/availability.
- tokeet_list_rates: All standard, dynamic and promotional rates of one rental. Read-only: rates cannot be changed with this server. GET /rate/{rental_pkey}.
- tokeet_list_guests: List guests (personal data: name, emails, phones, address, notes, interactions), one page at a time. Filter by partial name, booking source/channel, and whether they have bookings. GET /guest.
- tokeet_get_guest: One guest by id: contact details, notes, interactions and preferences. GET /guest/{pkey}.
- tokeet_get_guest_by_email: The guest whose primary email is exactly this address. GET /guest/email/{email}.
- tokeet_list_tasks: List the tasks (to-dos, e.g. cleanings and check-ins) in the account, sorted by task name. GET /task.
- tokeet_get_task: One task by id. GET /task/{task_pkey}.
- tokeet_list_expenses: List the expenses recorded in the account (date, rental, category, amount, paid/unpaid status), by creation date. Read-only. GET /expense.
- tokeet_get_expense: One expense by id. GET /expense/{expense_pkey}.
- tokeet_list_templates: List the message/email templates in the account, optionally of one type. GET /template.
- tokeet_get_template: One message template by id. GET /template/{template_pkey}.
- tokeet_list_triggers: List the automation triggers (event, rental, template, delay) in the account. Read-only: triggers cannot be changed with this server. GET /trigger.
- tokeet_create_guest: WRITE: create a guest record (name and email required, the rest optional). Nothing is sent to the guest. Tokeet cannot recover deleted data and this server cannot delete guests. POST /guest.
- tokeet_update_guest: WRITE: change fields of a guest (name, address, birthday, spouse, kids, drink, hobby, sport). Only the fields you pass are sent, and each one OVERWRITES the stored value (an address object replaces the whole address). Emails and phones have their own endpoints and are not changed
- tokeet_add_guest_note: WRITE: add an internal note to a guest record (not visible to or sent to the guest). POST /guest/{guest_pkey}/note.
- tokeet_record_guest_interaction: WRITE: log an interaction you had with a guest (phone call, meeting or comment) in the guest's history. Nothing is sent to the guest. `date` is an epoch timestamp: use the same unit as the dates you see on existing interactions from tokeet_get_guest. POST /guest/{guest_pkey}/inte
- tokeet_create_task: WRITE: create a task (to-do) in the account, optionally linked to an inquiry and assigned to a user. `due` is an epoch timestamp: use the same unit as the `due` of existing tasks from tokeet_list_tasks. No message is sent to anyone by this call. POST /task.
- tokeet_update_task: WRITE: change a task: rename, move to another list, reschedule, edit notes, reassign, or mark it completed (status 2) or active (1). Only the fields you pass are sent and each OVERWRITES the stored value. PUT /task/{task_pkey}.

Screening checks:
- MCP handshake: pass (Answered in 9ms)
- Domain against threat feeds (Cloudflare security DNS): pass (tokeet.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (24 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)