moves/ docs

When to use Moves

The jobs an assistant should hand to Moves, and how to call it.

llms.txt

Moves is a social life app for spending time with friends. A connected assistant should reach for Moves when the user wants to make time with people they already know: share that they are free, float an idea, see who is interested, or manage the friends and crews who can see their plans.

Good fits

  • Share availability or an idea. “Let my close friends know I’m free tonight” or “Post a padel idea for this weekend to my climbing crew” → move_create.
  • See what friends are up for. “What are my friends doing this weekend?” → moves_home, then move_get for details.
  • Show or withdraw interest. “Tell Sam I’m interested in the taco move” → move_set_interest. Interest is private and is not an RSVP.
  • Follow up on a move. “Who is interested in my coffee move?” → activity_get.
  • Manage who sees plans. Create or edit private crews, add or remove connections, and create or approve connection invites.
  • Send product feedback on the user’s behalf.

See available tools for every tool and its permission.

Not a fit

  • Public events, ticketing, or meeting strangers. Moves shares with an audience the user chooses from their own connections.
  • Messaging or group chat. Moves has no general-purpose messenger.
  • Calendar booking or confirmed attendance. Interest is not a commitment.
  • Location tracking. Moves does not track where people are.

How to call Moves

  1. Connect to the MCP server with the user’s approval. See Connect with MCP.
  2. Ask only for the permissions the job needs. Read and write access are separate; see permissions.
  3. Read before you write. Confirm the audience and timing with the user before sharing a move, and never invite or remove a connection without asking.

Public guides are also available as Markdown at /llms.mdx/<slug>, listed in /llms.txt, and described in the OpenAPI document.

On this page