Assist With Moving keeps the durable record. Your AI can research, organize, and save bounded work into it. Signing in proves who you are; the grant you approve afterwards decides what your AI may actually do. Create a fallback key only for local or non-OAuth tools.
What you will do
Simple connection setup
Approve only what the work needs. Your AI is shown just the tools your grant covers, and revoking it refuses the very next call.
https://movingmanifest.com/mcp
Paste this URL into any AI that speaks remote Streamable HTTP MCP with compatible OAuth. This is a capability requirement, not a claim that a particular AI product works — none has completed a full run yet, so the connection is Partial. Ask your AI to call describe_connection if no tools appear, get_move_brief first, search before creating duplicates, and use save_complete_result to keep finished decisions, estimates, plans, and source checks together.
The other doors are not the same: https://movingmanifest.com/mcp/connect keeps older connections working with a different, larger catalog; https://movingmanifest.com/api/mcp and the local assistwithmoving-mcp package take a scoped mmk_ key and never offer sign-in.
A fallback key can read and change your move data according to its scopes, and it is not governed by the grant. Only paste it into an AI you trust when the canonical connection is not available. Do not put keys in public chats, screenshots, issues, or documents. You can revoke connections and keys later in Settings.
Learn what your AI can help withYou do not need a connection at all to hand work over. Open a Queue item, copy its bounded brief into any AI, and paste the result back into the same item. The handoff completes without MCP, OAuth, or a key — and Settings → AI connections keeps a copyable brief ready for exactly this.
Read the MCP overview