# LifeClaw Muse connector

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

## LifeClaw

Search businesses and make phone calls to book appointments or ask questions

- Record: https://musedirectory.ai/connector/lifeclaw
- Category: Shopping & Commerce
- Developer: agentese.ai
- 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, sign-in needed, 1060ms, checked 2026-10-29T09:45:52Z
- Endpoint: https://api-v2.lifeclaw.agentese.ai/mcp
- Auth: Needs an access key; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T06:06:30Z)
- Source: Found in the official MCP Registry (ai.agentese.lifeclaw/lifeclaw) https://registry.modelcontextprotocol.io/v0/servers?search=ai.agentese.lifeclaw%2Flifeclaw

LifeClaw calls businesses to book reservations, make inquiries, and manage bookings. Search restaurants, salons, clinics and hotels by location, get details, and have Muse call to reserve or ask questions on your behalf.

Example request: "Find a sushi restaurant in Tokyo with availability and book a table for two tomorrow at 7 PM"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use LifeClaw to help me. It is a free service with an MCP server at https://api-v2.lifeclaw.agentese.ai/mcp. It needs an API key from agentese.ai; ask me to enter it through your secure credential prompt. 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:
- search_places: Search businesses (restaurants, salons, clinics, hotels…) by free text. `location` is REQUIRED and decides which country is searched — a city or country name ("Tokyo", "Singapore"). Returns up to `limit` places with a `cid` to pass to get_place. Costs 5 points. 
- get_place: Full details for one place from search_places: phone, hours, rating, website, booking link. Pass the same `location` you searched with. `phone_ref` is the handle call_business needs; when it is null the place cannot be called and `phone_ref_unavailable_reason` says why — show the
- call_business: Phone a business and wait for the outcome. `action="book"`: reserve. Required: merchant_name, date (YYYY-MM-DD), time_ (HH:MM, 24h), party_size, name; recommended: contact_phone (E.164). Both are the MERCHANT's local time. `action="inquiry"`: ask something — put the question in `
- modify_booking: Phone the venue to cancel or reschedule a confirmed booking from list_bookings. `action` is "cancel" or "reschedule"; reschedule needs new_date and/or new_time (merchant local). When the venue confirms, the booking record is updated for you. Same waiting and idempotency rules as 
- wait_for_call: Keep waiting for a call that call_business / modify_booking / call_person / call_me reported as in_progress. Returns the flat result once the call ends, or in_progress again — just call it again.
- list_bookings: The account's bookings (confirmed, cancelled, answered inquiries). `status` filters: "confirmed", "cancelled", "answered", or "" for all.
- account_status: Points balance, display name, and the selected receiving number for call_me (masked). Use receiving_phone_status for setup and caller_id_status for outbound display and outbound-display state. 300 points ≈ one minute of calling.
- receiving_phone_status: Check where call_me would ring (masked). A number must be explicitly selected and verified by voice; SMS login alone does not qualify. The user can set it in the web app without enabling outbound Caller ID. Direct them to setup_url if no receiving number is ready.
- caller_id_status: Check the owner's outbound Caller ID. Verified plus enabled display enables call_person. call_me uses a separate receiving number. If setup is needed, direct the user to `setup_url`: Settings → Caller ID, bind their own phone, answer Twilio's verification call and enter its code.
- list_contacts: List the token owner's saved contacts with masked phone numbers. Each contact_ref pins the current name and number for call_contact. If two names could match a request, ask the user to choose one exact name. Never repeat a full contact number in chat. 
- save_contact: Add or update one contact after confirming name and number with the user. phone_number must be E.164, e.g. +85291234567. This updates the same address book used by the web app. The result masks the number; do not echo the full number in a chat reply. Set user_confirmed only after
- update_contact: Edit a saved contact's name and/or E.164 phone number atomically. Confirm the existing contact and proposed change with the user first. A name conflict refuses instead of overwriting another person. Return values mask the number; do not repeat a full number in chat. 
- delete_contact: Delete a saved contact by exact name after the user confirms deletion.
- call_person: Call one private person and relay one message from the user. Ask the user to confirm the recipient, E.164 number and exact spoken message first, then set user_confirmed=true. `original_message` is the user's unedited request; `message` is the faithful sentence spoken aloud. Both 
- call_contact: Call a saved private contact without passing their full number. First list_contacts and confirm the chosen name, masked number and exact spoken message with the user. Pass that contact_ref and user_confirmed=true. If the contact changes before dialing, re-list and confirm again. 
- call_me: Ring the user's own phone, read them `message`, and bring back what they say. A phone call interrupts the user. Follow their explicit instructions about whether and when to call, including an immediate call or a call when a job finishes. Otherwise prefer chat for routine updates;

Screening checks:
- MCP handshake: pass (Answered in 1092ms)
- Domain against threat feeds (Cloudflare security DNS): pass (api-v2.lifeclaw.agentese.ai 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: warn (call_me: Unusually long tool description)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 210 days ago)
- AI review of purpose and tool behavior: pass (No concerns)