For AI apps that support MCP, MovingManifest provides a hosted OAuth endpoint plus an advanced remote API-key endpoint. The user still controls sign-in, connection access, fallback keys, and revocation.
MCP path
Assistant calls tools
User signs in to MovingManifest.
Assistant connects via hosted OAuth or the remote API-key door.
OAuth clients ask for consent; non-OAuth clients use a scoped key.
User can revoke the connection or key when finished.
MCP exposes structured tools for move setup, inventory intake, rooms, boxes, planning, photos, and capacity checks. Hosted OAuth defaults to a trusted-helper surface for normal move help.
Recommended: connect to https://movingmanifest.com/mcp and sign in with your MovingManifest account — no key to copy, works with your subscription. Advanced only: headless or non-OAuth agents connect directly to https://movingmanifest.com/api/mcp with a scoped API key.
Agents should call get_api_capabilities first, then get_api_context and get_agent_context before writing.
OAuth connections and API keys are revocable. Use API keys for headless or non-OAuth automation, and use separate keys for separate assistants when OAuth is not available.
The MCP tool list favors workflow operations such as setup_move, save_box_intake, batch_upsert_items, and apply_assignments so agents use fewer tokens and make fewer mistakes.
The public docs tell assistants not to invent access. Private move data requires the user to sign in with OAuth or intentionally create a scoped helper key.
OAuth-capable hosted assistants can connect without the user handling a raw secret. Settings manages revocation and API-key fallback for local or headless tools.
claude.ai, Claude Cowork, and other hosted MCP clients cannot run a local process. Add MovingManifest as a custom connector using the remote endpoint. OAuth-capable clients open MovingManifest sign-in and consent instead of asking the user to paste a key.
MCP endpoint (recommended)
https://movingmanifest.com/mcp
OAuth-capable hosted clients
Paste this MCP URL into an OAuth-capable hosted client (recommended): https://movingmanifest.com/mcp Then sign in with your MovingManifest account — no key needed. The client discovers Clerk auth from: /.well-known/oauth-protected-resource/mcp
Advanced: API-key door (headless / non-OAuth only)
Advanced — headless / non-OAuth clients ONLY. This door is key-only and rejects OAuth sign-in; do not use it for hosted clients. POST https://movingmanifest.com/api/mcp Authorization: Bearer mmk_replace_with_a_scoped_api_key
In claude.ai or Claude Cowork: Settings → Connectors → Add custom connector and paste the endpoint URL. If the client does not support OAuth, create a scoped helper key and supply it as the bearer token (or an x-api-key header). Do not paste raw keys into OAuth-capable hosted clients. Passing the key in the URL (?key=...) is no longer supported — URLs get logged, so a key that has ever been in one should be rotated.
OAuth-capable CLI and desktop agents should use the same hosted endpoint as other clients. When OAuth is unavailable, connect directly to the remote API-key door and read the key from an environment variable. The API-key surface can expose broader tools when the user grants those scopes intentionally.
Codex OAuth setup (recommended)
codex mcp add movingmanifest --url https://movingmanifest.com/mcp codex mcp login movingmanifest
Codex API-key setup (advanced)
export MOVINGMANIFEST_API_KEY=mmk_replace_with_a_scoped_api_key codex mcp add movingmanifest \ --url https://movingmanifest.com/api/mcp \ --bearer-token-env-var MOVINGMANIFEST_API_KEY
Equivalent advanced Codex config.toml
[mcp_servers.movingmanifest] url = "https://movingmanifest.com/api/mcp" bearer_token_env_var = "MOVINGMANIFEST_API_KEY"
Keep the key in your shell or secret manager, not in the checked-in config. Restart Codex after adding the server. In a new Codex thread, check MCP tools for movingmanifest, then call get_api_context.
The hosted OAuth launch surface is a trusted-helper set: enough for move setup, item intake, photos, boxes, transport planning, and review, without publicly advertising sale, export, household admin, or low-level box primitives as hosted-default tools.
Start here: get_api_capabilities, get_api_context
Move context: list_moves, setup_move, get_move_summary, get_agent_context, get_move_questions, get_move_day_checklist
Inventory workflows: search_inventory, save_box_intake, add_item_from_photo, batch_upsert_items
Box workflow: save_box_intake for one box, dimensions, weight, photos, described contents, and linked existing items
Photos and evidence: upload_photo, upload_photos, upload_evidence_image, upload_evidence_images
Spaces and planning: list_move_spaces, create_move_space, suggest_assignments, apply_assignments
Move-day and planning helpers: list_planned_items, create_planned_item, update_planned_item
Available when a user intentionally grants a broader API-key connection.
Move creation and setup for headless automations
Detailed item and box primitives for advanced partial workflows
Sale-prep workflows when the user grants that scope intentionally
Export and share workflows when the user grants documentation access
Household collaborator management for admin-approved local helpers
Layout Studio operations for plan review and editing
Raw upload sessions for clients that cannot use workflow photo tools