Troubleshooting
Help with connecting, permissions, and screen sharing.
The connection does not start
- Use the product app URL ending in
/api/mcp, not the docs URL. - Check that your assistant supports remote Streamable HTTP and OAuth. A client that only accepts a local command or a static API key cannot use this flow.
- Hosted connections need HTTPS and a server reachable by your assistant. An assistant running in the cloud cannot reach a server on your computer's localhost.
- If a preview opens a hosting-provider password screen, its owner needs to make the MCP and OAuth endpoints accessible before you can connect.
Sign-in or approval fails
Use an existing Moves account. Check the sign-in method available on the Moves page. If consent was cancelled or took too long, start again from your assistant. Do not reuse an old approval link.
A tool asks for more permissions
Seeing a tool in the list does not mean you approved access to it. Ask your
assistant to reconnect with the required permission.
For example, sharing a move requires moves:write, even if reading with
moves:read works. Existing connections do not automatically gain the new social
permissions. If the client registered a restricted scope list, it may need to
register again before requesting them.
My connection stopped working
The grant may have expired or been disconnected. Reconnect and approve access again. If it still fails, check that your assistant supports the server's OAuth flow. Provider compatibility is still being verified.
Profile settings are empty
profile_get returns null when you have not created settings. Creating them
requires profile:write; an empty read result is not a sign-in failure.
My assistant cannot see my screen
Check all three: the connection has context:read, you selected a source for that
assistant, and that source is active. In the web app, enable Share this tab
again after a reload or expiry. After an app restart, select the new source.
A change timed out
Read the affected moves, crews, invites, settings, or feedback before retrying. The change may have completed even if your assistant did not receive the response. In particular, retrying a create tool can duplicate records. Invite tokens are returned only once and cannot be recovered from the invite list.