Install

1. Connect your account

uvx moveo-one-mcp login

This opens your browser to approve access. Credentials are cached in your OS keychain, falling back to a 0600 file at ~/.moveo/credentials.json.

uvx comes with uv. It runs the server without installing it globally, so you always get the current version.

To disconnect:

uvx moveo-one-mcp logout

This clears stored credentials for the current environment.

2. Register the server

Claude Code

claude mcp add moveo-one -- uvx moveo-one-mcp

Claude Desktop

In claude_desktop_config.json:

{
  "mcpServers": {
    "moveo-one": {
      "command": "uvx",
      "args": ["moveo-one-mcp"]
    }
  }
}

Cursor and other stdio clients

Any client that launches an MCP server as a subprocess takes the same command (uvx) and argument (moveo-one-mcp). Consult your client's MCP configuration docs for where that goes.

Remote clients

For clients that support remote MCP servers over streamable HTTP with OAuth 2.1, point them at:

https://hound.moveo.one

Same tools, minus the ones that read and write your local filesystem.

3. Check the connection

Ask your assistant to run whoami. It reports the connected account and the projects it can reach. If it says you are not connected, run uvx moveo-one-mcp login again.

list_projects shows which workspaces you have access to.

Configuration

Set these in the env block of your MCP client's server entry:

Variable	Default	Meaning
MOVEO_ENV	prod	prod, dev, or local — selects backend and app URLs
MOVEO_API_BASE_URL	derived from MOVEO_ENV	Override the backend URL
MOVEO_REQUEST_TIMEOUT_SECONDS	75	Per-request HTTP timeout

Example:

{
  "mcpServers": {
    "moveo-one": {
      "command": "uvx",
      "args": ["moveo-one-mcp"],
      "env": { "MOVEO_REQUEST_TIMEOUT_SECONDS": "120" }
    }
  }
}

Credentials are stored per environment, so a dev login does not overwrite a prod one.

Headless clients

For n8n, CI, or anything that cannot complete a browser flow, create a personal API token in the Moveo One app and supply it to the client instead of running login.

caution

A personal API token carries your own access. Store it the way you store any other credential — in your CI secret store, never in a committed file.

Troubleshooting

"Not connected" after logging in. Check MOVEO_ENV matches the environment you logged into. Credentials are stored per environment.

A tool times out. Some calls are genuinely slow — analytics questions over large date ranges especially. Raise MOVEO_REQUEST_TIMEOUT_SECONDS.

Filesystem tools are missing. You are on the hosted server. They register only in local mode, by design.

A simulation tool says the run will take hours. It will. Quantum runs are long; the assistant polls rather than blocking. See Quantum.