moves/ docs

Connect with MCP

Give your assistant access to Moves in a few steps.

llms.txt

Before you begin

You need an existing Moves account and an assistant that supports remote MCP over Streamable HTTP with OAuth sign-in. Create your Moves account in the iOS app if you do not have one yet.

Server address

MCP server URL
https://app.whatsthemove.social/api/mcp

Manage connected assistants to review access or disconnect an assistant.

The server lives on the Moves product app, at /api/mcp. The address of this documentation site is not the MCP server address.

Connect your account

  1. Open your assistant's integrations or MCP settings and add a remote server.
  2. Name it Moves and paste the server URL above.
  3. Start the connection. Your assistant opens a Moves sign-in page.
  4. Sign in, check the assistant name and callback host, and review its requested permissions. Write access includes deletion.
  5. Approve the connection, then return to your assistant.

No API key is needed. Your assistant handles OAuth registration and sign-in; do not paste your Moves password into a chat or a server configuration.

Try a read first

Ask: “Show my Moves profile settings.” This needs profile:read. If no settings exist yet, the result is empty. That does not mean the connection failed. Creating settings requires separate write access.

For more actions, see available tools.

Share your current screen

Screen context is optional. Request context:read and select a source during consent or in Connected assistants. In the web app, first choose Share this tab. The signed-in iOS app reports its current screen while active; an assistant can only read it once you select that source for its connection.

New sources, including those created after an app restart, need to be selected again. See screen sharing and privacy.

Disconnect

Open Connected assistants in Moves and disconnect the assistant. Signing out of Moves alone does not revoke an assistant's separate connection.

On this page